Assuming that you have an Ignite-UX server in your environment, you can use the make_net_recovery command.
Some of the invocations of make_net_recovery are as below.
These commands are executed from the HP-UX server which is a client to the Ignite-UX server.
make_net_recovery -v -s <Ignite-UX_server_name> -x inc_entire=vg00
The above takes a verbose mode Ignite-UX make_net_recovery backup to the Ignite sever. It os noteworthy that by default the make_net_recovery archive of the client is put at the /var/opt/ignite/recovery/archives/<hostname> directory on the Ignite-UX server, where <hostname> is the client name for which you are making an archive in make_net_recovery format.
The above also updates the client information for the recent backup being taken for the client on the clients folder of the Ignite-UX server, the location on the Ignite-UX server being /var/opt/ignite/clients/<hostname>. Where hostname is the name of the client which you are creating a network make_net_recovery archive for.
make_net_recovery -v -s <Ignite-UX_server> -a <Archive_server>:<Archive_location>-x inc_entire=vg00 -x exclude=/var/adm/crash
In the above case my Ignite-UX server is different from the Network archive server and I want to exclude /var/adm/crash of the client from being backed up.
To be noted that the Ignite-UX backup takes help of NFS in the background where the Ignite-UX server and the archive server (in case in your environment the Ignite-UX and the archive servers are different) work as NFS server and the client is an NFS client.
This mandates that the folders /var/opt/ignite/recovery/archives and /var/opt/ignite/clients are NFS exported for read/write and access from the client which is being backed up.
To be more specific you can give access to the Ignite-UX clients in a more restrictive manner by exporting the individual /var/opt/ignite/recovery/archives/<hostname> and /var/opt/ignite/clients/<hostname> to the specific client (hostname which is being backed up using make_net_recovery) something like below.
/etc/exports on Ignite-UX server
/var/opt/ignite/clients/host1 -anon=2,access=host1.example.com:host1
/var/opt/ignite/recovery/archives/host1 -anon=2,access=host1.example.com:host1
Please note that if FQDN is used in your environment use of the FQDN as above helps to overcome some permission denied error messages.
-anon=2 above means that during the backup the userid "bin" is being used for NFS mounts to mount and write to the /var/opt/ignite/clients/<hostname> and /var/opt/ignite/recovery/archives/<hostname>
No comments:
Post a Comment