make_net_recovery obscurities

[Ralph Grothe]

Hello,

currently I'm experimenting with creation of recovery images of clients on an Ignite server, but already fail when I try to execute the make_net_recovery on the client.

For my first trial I created this FS on the would be Ignite server (5 gigs should suffice during this stage):

# bdf /var/opt/ignite/clients
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol16 5120000 2432 5077600 0% /var/opt/ignite/clients


The required Ignite SW as well as patches are installed on both client and server (both run HP-UX 11.11)

e.g.

# swlist|grep -i ignite
B5725AA B.3.7.95 HP-UX Installation Utilities (Ign
ite-UX)
Ignite-UX-11-11 B.3.7.95 HP-UX Installation Utilities for
Installing 11.11 Systems
PHSS_27406 1.0 Ignite-UX make_medialif patch


I then ran the command "ignite" as root on the designated Ignite server, and ran through the initial server configuration (e.g. assigning range of initial boot IPs etc.)

After that on the Ignite server there seems to be installed a basic set of network recovery tools for the clients to fetch:

# du -skx /var/opt/ignite/depots/recovery_cmds/
512 /var/opt/ignite/depots/recovery_cmds/

It also exported my FS to take up the clients' depots:

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

RPC deamons are also running

# ps -ef|grep -e rpc -e bio -e nfsd|sort -u -k 9,|grep -v grep
root 1107 1 0 Oct 11 ? 1:00 /opt/dce/sbin/rpcd
root 705 1 0 Oct 11 ? 0:12 /usr/sbin/biod 16
root 1438 1 0 Oct 11 ? 0:00 /usr/sbin/nfsd 16
root 734 1 0 Oct 11 ? 0:00 /usr/sbin/rpc.lockd
root 1427 1 0 Oct 11 ? 0:00 /usr/sbin/rpc.mountd
root 728 1 0 Oct 11 ? 0:00 /usr/sbin/rpc.statd
root 681 1 0 Oct 11 ? 0:00 /usr/sbin/rpcbind


Client and server reside in the same LAN and are accessible (e.g. via ssh) from both directions.
Name resolution (based on node name) also works.

I even created an .rhost for automated root logins on the client from the server (though I despise this since we only use ssh), because I felt I thus had to account for the error messages I keep receiving.

When I now run make_net_recovery on the client in order to create a boot image from the client and transmit it to the Ignite server, I get these silly messges (mind you, I'm running this as root):

# /opt/ignite/bin/make_net_recovery -v -s don -x inc_entire=vg00
* Creating NFS mount directories for configuration files.
ERROR: Could not make directory:
/var/opt/ignite/recovery/client_mnt/0x080009559A69: Permission denied
(errno = 13)
ERROR: Failed creating the directory
/var/opt/ignite/recovery/client_mnt/0x080009559A69:Permission denied
(errno = 13)
ERROR: Failed to creaet NFS mount directories for configuration files.

======= 10/23/02 18:26:24 METDST make_net_recovery completed unsuccessfully


eh, so what?

# whoami;ll -d /var/opt/ignite/recovery/client_mnt
root
drwxr-xr-x 2 bin bin 96 Oct 23 17:44 /var/opt/ignite/recove
ry/client_mnt


The same sort of error messages appear when I try to "add a new client" from within the ignite program on the server.

What am I missing here?

[Sandip Ghosh]

You have to export /var/opt/ignite instead of /var/op/ignite/client. Because it is trying to create the directory as /var/opt/ignite/recovery/client_mnt. And also look at the permissions of the directory as described in the manual.

Sandip

[Jean-Louis Phelix]

Hi,

I full agree ... From make_net_recovery man page, you have a section "Exporting Archive Directory". Here you will find :

+ 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

Regards,

Jean-Louis.

[Ralph Grothe]

I have to admit I should have read the manual page of make_net_recovery more carefully.
There indeed it is explicitly stated which directory to export on the archiving server (in my case this should be the same machine as the Ignite server).

But now I'm a bit confused because

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

was automatically exported by the Ignite server when I went through the initial setup.
I now need to know (for diskspace requirements' sake) which of the two mandatory exports will take up the bulk of data (I'm a bit short of disk space at the moment)?
From an intuitive understanding I would think that the (default) export for the archive will take up the most data whereas the export from the Ignite part only stores some meta data and custom tools for the client to boot over the network.
But I really have no notion here.

[Jean-Louis Phelix]

hi,

The "small" part is in /var/opt/ignite/client, but the location of the "big" part, the archive itself is by default /var/opt/ignite/recovery/archives/, which can be changed using -a option.

Regards,

Jean-Louis.