Network Ignite

[Duffs]

I am trying to take an ignite backup of a HP-UX server (host B) over the network.
(Host A & B are not the real hostnames).

hostA - Ignite Server (HP-UX 11.23)
hostB - HP-UX 11.23

Host A is the ignite server with file system /var/opt/ignite/clients (dynamic link to /ignite/recovery) containing 150G of disk space.

Host B contains an NFS mount point (/ignite) to host A:/ignite/.

I get the following error when I run 'make_net_recovery':


Host B:/#make_net_recovery -s -a :/ignite/recovery –A

* Creating NFS mount directories for configuration files.
nfs mount: get_fh: Host A:: RPC: Rpcbind failure - RPC: Timed out
NOTE: run_cmd: Process: 29178 (/usr/sbin/mount): killed by signal: 2.
ERROR: Could not NFS mount directory /var/opt/ignite/clients on Host A.
If the OS on the Host A is 11.31 or later, the dfstab file on
Host A should contain the entry "share -F nfs -o anon=2
/var/opt/ignite/clients". Ensure that /var/opt/ignite/clients has
been exported using the "shareall -F nfs" command. Otherwise, the
exports file on 10.18.118.69 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:/No such
file or directory (errno = 2)
ERROR: Failed to create NFS mount directories for configuration files.

======= 08/20/09 14:56:31 BST make_net_recovery completed unsuccessfully

I can successfully mount the /var/opt/ignite/clients dir from my ignite server (Host A) on the client server:
# mount Host A:/var/opt/ignite/clients /ignite



Host A # swlist | grep -i ignite
IGNITE C.7.6.98 HP-UX Installation Utilities (Ignite-UX)
Ignite-UX-11-23 C.7.6.98 HP-UX Installation Utilities for Installing 11.23 Systems
Ignite-UX-11-31 C.7.6.98 HP-UX Installation Utilities for Installing 11.31 Systems

Host B # swlist|grep -i ignite
IGNITE C.7.4.155 HP-UX Installation Utilities (Ignite-UX)
Ignite-UX-11-23 C.7.4.155 HP-UX Installation Utilities for Installing 11.23 Systems

Could this be a version issue?

R,
D.

[Steve Steel]

Hi


Look at

http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1060231

Steve Steel

[Duffs]

Hi Steve,

Thanks for the link but unfortunately it is of no help.

R,
D.

[Duffs]

Ok, I have changed the location of the location to /var/opt/ignite/clients and have overcome the probloem with another:

ERROR: Cannot retrieve Ignite-UX version from server "Host_A".
ERROR: Retrieving Ignite-UX version on the server:Host_A failed.

I don't think it actually a version issue, nor does it appear to be an swacl issue:

Host_A#swacl -l host
any_other:-r---

R,
D.

[Mel Burslan]

Are you sure HostA is running an NFS server and successfully exporting the ignite filesystem to HostB with write permission ? Without the help from ignite, try mounting the NFS filesystem from HostA while logged into HostB and create a dummy file in the ignite structure where the archive of this server is supposed to be. More than likely it will error out. It might be due to HostA's NFS server configuration or due to some firewall in between blocking access from one server to the other via NFS required ports (and if the firewall is inspecting packets statefully, it might also be blocking NFS packets as well).

Hope this helps

[Sudeesh]

1. Ignite server should NFS export /var/opt/ignite/clients and /var/opt/ignite/recovery/archives in rw mode.
2. NFS server daemon should be running on ignite server.
3. Ensure client is able to mount the nfs export.

4. try running the command.

[Duffs]

Hi,

The NFS mount options are fine as I can manually mount the ignite server FS on the client.

R,
D.

[Steven E. Protter]

I know this is an old case.

But I found it and solved it.

I made the leap of intellect today that when Ignite can't get the version number of Ignite, it was trying to use swlist.

True enough, swlist could not execute.

In our case that was because we use etrust and the swlist binary had become untrusted.

But when you get this message, run a simple swlist command and eliminate something dorky like what brought me to this case.

SEP