recover a HP-UX 11.23 system from make_net_recovery backup of another system

[santosh jha]

Hi ,

Is is possible to recover a HP-UX 11.23 system from make_net_recovery backup of another system
which are almost same in configuration and hardware.

If yes ,Could you gimme the procedure for that.

[Steven E. Protter]

Shalom,

This question was asked yesterday.

This will work.

You boot the system, intervene when prompted, tell the system via the menu to boot off the network. You can specify the server the image resides on.

You will then need to intervene when Ignite offers you this chance and check the hardware, network,hostname,ip address and other information.

Then you are pretty much done, waiting for the process to complete.

SEP

[santosh jha]

I didn't really understand where i will get the opyions.

[DCE]

yes you should be able to

boot the client system
interupt the boot process

issue bo lan.ip_address_ignite_server install

at the menu that comes up
Select Install HP-UX
Select Advanced Installation

on the basic tab select additional options
set cloning to new hardware=true

under system tab
verify system name

[Jaime Bolanos Rojas.]

Santosh,

Also this link you will give some more detail on how to proceed,

http://docs.hp.com/en/B2355-90970/ch09s06.html

Regards,

Jaime.

[santosh jha]

Hi Guys i am getting error after doing as you said.

I can see the recovery archive from my source server but gives me error like

"The currently selected configuration contains no primary swap definition."

"The currently selected configuration contains no disk layout selections"

"When the File System layout changes, the "Root Swap" value may be reset."

" Could not locate the _hp_disk_layout variable "

[santosh jha]

I am getting this error now.

Permission denied
NOTE: Retrying: "/sbin/fs/nfs/mount -oro
170.86.41.90:/var/opt/ignite/recovery/archives/wallace
/tmp/ign_configure/archive_nfs"
Permission denied
NOTE: Retrying: "/sbin/fs/nfs/mount -oro
170.86.41.90:/var/opt/ignite/recovery/archives/wallace
/tmp/ign_configure/archive_nfs"
Permission denied
NOTE: Retrying: "/sbin/fs/nfs/mount -oro
170.86.41.90:/var/opt/ignite/recovery/archives/wallace
/tmp/ign_configure/archive_nfs"
Permission denied
NOTE: Retrying: "/sbin/fs/nfs/mount -oro
170.86.41.90:/var/opt/ignite/recovery/archives/wallace
/tmp/ign_configure/archive_nfs"
Permission denied
NOTE: NFS mount (/sbin/fs/nfs/mount -oro
170.86.41.90:/var/opt/ignite/recovery/archives/wallace
/tmp/ign_configure/archive_nfs) failed, see messages above.
ERROR: Command "/sbin/fs/nfs/mount -oro
170.86.41.90:/var/opt/ignite/recovery/archives/wallace
/tmp/ign_configure/archive_nfs" failed. Ensure that
"/var/opt/ignite/recovery/archives/wallace" is properly exported on
170.86.41.90.
ERROR: Cannot load OS archive(s) (Recovery Archive)

The configuration process has incurred an error, would you like
to push a shell for debugging purposes? (y/[n]):

PLEASE HELP.

[DCE]

Did you do the following from the ignite manual?

Step 1. Use make_net_recovery or Ignite-UX to create a system recovery image
of the source system.
Step 2. On the Ignite-UX server, if the client to be installed does not currently
have a directory in /var/opt/ignite/clients but is up and running,
use the Ignite-UX GUI to create that directory using Add New Client for
Recovery from the Actions menu. For more information, see â Adding
Clients for Recoveryâ on page 231.
System Recovery
Notes on Cloning Systems
246 Chapter 9
If the client is not running, you will either need to boot it from the
Ignite-UX server or from a tape made with make_boot_tape in order for
this directory to be created.
Step 3. Copy the CINDEX and recovery directory from a source client to the target
client directory. If the target client has previously used
make_net_recovery, it will already have a CINDEX file. If the CINDEX
file for the client exists, you may want to save a copy and/or edit the file
to add the desired entries from the source client. The following
commands copy the required files. You may specify src_client and
target_client using either the LAN addresses (such as
0x0060B04AAB30), or by using the clientâ s hostname (which is a symlink
to the LAN address):
cd /var/opt/ignite/clients/src_client
find CINDEX recovery | cpio -pdvma ../target_client
Step 4. Give the target client NFS access to the archive of the source system. To
do this, log in to the system that holds the archive (normally the
Ignite-UX server).
Typically each target client has its own directory for storing the archives,
and the directory is exported only to the individual client. In this case,
you will need to edit the /etc/exports file to allow access to both the
source and target clients:
a. Enter vi /etc/exports
b. Append: target-client to the end of the source-clientâ s line.
c. Enter exportfs -av
Step 5. Boot the target client from the Ignite-UX server (using any method you
want). Then, when you install the system you can select from the
recovery configurations of the source system.
Step 6. Change the system networking parameters for the client during the
installation.
For additional information regarding system cloning, see the Cloning
and Recovery Issues using Ignite-UX White Paper on the "Information
Library" page available at the Ignite-UX Web site at:
http://www.docs.hp.com/en/IUX/infolib.html
System

[santosh jha]

YES