/var/opt/ignite/clients directory - can it be moved?

[Lance McGrath]

All -

I'm looking to move the clients directory to a different location, and I'm wondering if it's possible. Searching the almighty google hasn't gotten me anywhere yet. :-)

We use a lot of network attached storage in our environment, and I decided to mount /var/opt/ignite from the netapp for a variety of reasons:
1) If we lost the ignite server, all I'd have to do is install another server, point it to that directory, and I'd be ready to go again.
2) The netapps have much faster network connections than the server and much better redundancy. In my configuration files, I actually pull the depots and golden images down from the netapp directly, bypassing the ignite server.

However, that export on the netapp is read/write only to the ignite server. It's read only to everything else. On top of that, you obviously can't export a directory that you've mounted from somewhere else. So what appears to be the simplest solution to my problem is to give ignite a different location for the clients directory. Can anyone tell me how to do that?

Thanks!
Lance

[Steven E. Protter]

You can do this.

You will need to go through your Ignite INDEX and other configuration files and point them the right way.

If this is an NFS connection, you may have to deal with some congestion issues as well.

All of the configuration files are in /opt/ignite or the /var system.

Take your time, change and test.

SEP

[Bob_Vance]

>solution to my problem

What problem?
I'm not understanding the question, because the answer seems too simple:

Just move the /var/opt/ignite/clients directory to wherever you want and make a symbolic link from /var/opt/ignite/clients to the new location.

That just can't be what you're asking ;>)


hth
bv

[Lance McGrath]

Thanks Steve, I'll give that a whirl. Grepped through the files in /opt/ignite, looksl like I've got more than a dozen to change, although some are doc files.

Unfortunately, Bob, it's not quite that simple, because you can't share a remotely mounted filesystem. Even though the link points back to the local filesystem, it still can't be mounted. :(

Lance

[harry d brown jr]

If it's a disk space issue, you can have /var/opt/ignite/clients be it's own Logical Volume (lv) making it available for NFS mounting.

live free or die
harry d brown jr

[Lance McGrath]

Well, it turned out that finding every file where /var/opt/ignite/clients (or /var/opt/ignite/$CLIENT_MNT_DIR) was explicitly mentioned was an incredible pain. So I got smart about it and just moved everything from within /var/opt/ignite/ to /da/adm/data/ignite (our network-mounted location) EXCEPT the clients folder. Then I created links for each file / directory from the original dir to the new one. Same benefits as running the whole thing from the network, less work than trying to modify all those config files. Thanks for all your help!

Lance

[Jeff Hoevenaar]

I had the same problem and here is what I did.

I created a new directory: /silo/ignite
I linked /var/opt/ignite to /silo/ignite

When I tried to add a client the nfs failed becuase of the link.
So I manually exported /silo/ignite/clients
Then I added a client to ignite and it worked. It picked up the /silo/ignite/clients export.

How this will react with a restore is yet to be seen.