Operating System - HP-UX
1847585 Members
2963 Online
110265 Solutions
New Discussion

make_net_recovery problems

 
SOLVED
Go to solution
Greg Traud_2
Frequent Advisor

make_net_recovery problems

I've created an Ignite server, and allocated quite a bit of space to it in the hope that I can use make_net_recovery to back up several other HPUX servers over the network. My ignite server is called sbbakup2, and the server I want to backup is called sbset01.
I am very new when it comes to creating/using an ignite server. Previously, we've just used attached tape drives. However we have an inordinate investment in dedicated tape drives, that I'm trying to get away from.

Anyway, here's what happens:
root@SBSET01 [/opt/ignite/bin]
# make_net_recovery -s sbbakup2 -i
* Creating NFS mount directories for configuration files.
ERROR: Could not open /var/opt/ignite/recovery/client_mnt to determine
existing lanic id's:Permission denied (errno = 13)
ERROR: No lanic id value could be assigned. This value is required to create
the directory which stores system recovery configuration files

ERROR: Failed to create NFS mount directories for configuration files.

======= 11/02/06 15:22:56 EST make_net_recovery completed unsuccessfully



Hopefully, this is something simple I've overlooked.
5 REPLIES 5
Calandrello
Trusted Contributor

Re: make_net_recovery problems

Friend you have some mounted NFS, or ja had in this schemes?
Yang Qin_1
Honored Contributor
Solution

Re: make_net_recovery problems

Did you follow this procedure?

+ On the archive server, create a directory for each client to hold
the archive of the client's files. It is important that the
directory be owned by the user "bin". Replace in the
commands below with the hostname of the client. If you use the -a
option to make_net_recovery to specify an alternate location for
the archives, you will need to use that path instead of the
default which is shown below.

mkdir -p /var/opt/ignite/recovery/archives/
chown bin:bin /var/opt/ignite/recovery/archives/

+ Edit /etc/exports to add an entry for each client. Replace
with the client's hostname in the example shown:

/var/opt/ignite/recovery/archives/ -anon=2,access=

+ Run the exportfs command to have the edits to the exports file
take effect:

/usr/sbin/exportfs -av


Yang
Denver Osborn
Honored Contributor

Re: make_net_recovery problems

Do you have the IUX clients dir exported from the server side?

Check /etc/exports on IUX server for...

/var/opt/ignite/clients -anon=2

You should also have an archive directory exported to the client... man make_net_recovery.

Hope this helps,
-denver

Greg Traud_2
Frequent Advisor

Re: make_net_recovery problems

Some additional info which may help:

sbset01 is running 11.23, and sbbakup2 is running 11.11.

When I modified the command to:
make_net_recovery -s localhost -i

in order to use the ignite utility installed on the sbset01 server, things worked much better.

Thank you all very much for your prompt replies.
Greg Traud_2
Frequent Advisor

Re: make_net_recovery problems

I didn't have the 'ALL OS' version of Ignite installed on the ignite server sbbakup2. (I'll correct that shortly.)
When I used the ignite utility installed on the server sbset01, and followed the prompts, it worked.