Ignite and NFS (and NetApp NFS)

[Paul Murray_4]

Hello All,

We have two Ignite servers, one production and one for DR purposes.

In order to keep these in sync with each other, the data, archives, recovery and client directories are stored on an NetApp filer.

However, when trying to perform an installation, or a make_net_recovery, I get NFS errors with the usual exportfs type of messages.

I am presuming that the errors are being issued because the Ignite server is trying to export it's /var/opt/ignite/* directories, which are in turn mounted from an NFS source.

Has anyone else tried something similar ???

Thanks in advance for any/all help !!!

Regs,
Paul.

[RAC_1]

If I understood your post correctly you can export a exported file system. (a nfs FS can not be exported further)

also what the exact error message you are getting.

Anil

[Paul Murray_4]

Hi Anil,

The error from a make_net_recovery session is :

* Creating NFS mount directories for configuration files.
Permission denied
ERROR: Could not NFS mount directory /var/opt/ignite/clients on lntrs147. The
exports file on lntrs147 should contain the entry
"/var/opt/ignite/clients -anon=2". Ensure that /var/opt/ignite/clients
has been exported using the "exportfs -av" command.
ERROR: Failed mounting directory /var/opt/ignite/recovery/client_mnt:/Error 0
(errno = 0)
ERROR: Failed to creaet NFS mount directories for configuration files.

======= 10/13/04 14:01:23 BST make_net_recovery completed unsuccessfully



If I cannot place my archives on our NetApp NFS server, what would be the best way to keep two Ignite servers in sync ?

(Thanks again).

Paul.

[Michael Roberts_3]

You _can_ have your archives on a server other than the ignite server. The messages are complaining about the /var/opt/ignite/clients mount which _is_ the server. On the machine you are creating the archive for (client) can you by hand mount the Ignite server? Eg.
mount iuxserver:/var/opt/ignite/clients /var/tmp/testmount

[RAC_1]

Are you rnnning the make_net_recovery command as root?? If yes, you need to know that the root is always treated as anonymous user.

You will have to specify option "root=client_from_which_you_are_running_net_recovery" on the ignite server and export the file system.

Is you are using ignite gui to make the net recovery, as the error message says, add option anon-2 and try.

Anil

[Paul Murray_4]

Hi Michael,

I think, as was stated earlier, that the problem is because I am mounting the archive directory from our NFS server.

Basically, the setup is :

NFS Server
----------
archives directory
recovery directory
clients directory

Ignite Server
-------------
All local files
NFS mounts to archive, clients and recovery.


If I try to re-export the /var/opt/ignite/clients on our Ignite server, I receive the error:

exportfs error: /cm/ignite/clients: Too many levels of remote in path.


Any ideas ????

[Michael Roberts_3]

the archive access can be handled with the nfs_source = line in the archive
config file, and it would point to your NetApp server.

the client specific directory mounts are driven from the 'server=' line in
the INSTALLFS. This will be harder to deal with since the load of the
bootstrap commands is also driven from this variable, ie. if you changed
'server=' to be the NetApp server then you would get tftp errors for
INSTCMDS and SYSCMDS.

I suppose you could try setting up the NetApp machine to be able to tftp,
NFS mount the /opt/ignite/data and /var/opt/ignite ( for INDEX and script
access) from the Ignite server to the NetApp server. Then set the 'server='
line in the INSTALLFS to the NetApp server. This doesn't solve the problem
of trying to write to the per-client log file, but you might get further.

BTW, I tried using LOFS mount of an NFS mounted directory and re-exporting
it. The system was smarter than me and figured out that there was an NFS
mount in the mix.

[Steven E. Protter · Accepted solution]

You probably can keep a copy of your ignite configuration/client files on the NetApp filer. What you can't do is have Ignite function properly because you can't nfs export an exported folder.

What I'd actually do to keep things in synch is an automated regular scp(openssh) transfer.

Create and exchange public keys (see attached doc) and cron can scp files between the two /var/opt/ignite directories as often as necessary.

Then both servers can properly export /var/opt/ignite and function independently, re always being there when one or the other goes POOF.

openssh/secureshell
http://software.hp.com/portal/swdepot/displayProductInfo.do?productNumber=T1471AA

Price is right. Free!

SEP

[Paul Murray_4]

Guys,

Thanks for all your help.

I'm gonna do a mix of the local clients directory (sync'ing with a nightly script), whilst putting the archives on NFS (and change the nfs_source).

Thanks again - Paul.