Test recovery archive created over network

[Vaish Raj]

I created a system recovery archive of HP 11.0 client(no local tape drive) from HP 11i Ignite server(local tape drive exists) using make_net_recovery. I created archive of complete vg00 of client.

The log file at the end shows as "make_net_recovery completed successfully".

I want to test recovery of HP 11.0 client using created archive like :

1) Restore few files from archive over network.

2) Boot HP 11.0 client from HP 11i Ignite server over network.

3) Any other method of testing to make sure archive is fine in case i have to recover.

4) Make tape of created client archive.

Can someone give details if we can achieve and how to achieve all above point by point

Thanks

[Mel Burslan]

The answers to your questions may not be what you are expecting but here it goes:

1. you can not restore just a few files from your ignite archive, using conventional methods, over the network. This archive is put together to recover the whole system, not just a few files. So, to test the integrity of the archive, you need to find a system with a nearly identical hardware infrastructure to the one backed up, then boot this new server from the newly created ignite image, i.e., if your original server was an L class machine, your test target had better be an L-class as well.

2. assume your ignite server's ip address, reachable from the subnet where the system to be recovered is 11.22.33.44 (totally ficticious) then you go to the console of your server to be recovered/installed, shut it down or if it is already down, issue an RS command from the GSP (or equivalent) prompt. When you see "press any key to interrupt the boot process" notice, interrupt it. then at the menu prompt, type :

boot lan.11.22.33.44 install

notice the dot between lan and 11 as the characters used on the forum makes it almost invisible but it is a dot, not a space.

this will boot you up to a mini kernel and will give you the hpux install menu interface. Choose install hpux option and let it load the install interface.

At this point, where you see the mission critical or technical server etc. options, you will see the name of your image you just created in the drop down menu. Select the image you just created and let go.

Make sure either your original system is offline or change the IP address of the new test system to prevent ip address conflicts. you can do this under system tab in the install interface.

3. there are no other methods than actually igniting a server to test the full integrity of an archive that I know of

4. if you want a bbt (bootable backup tape) you need to create it using make_tape_recovery command (see man pages for all of the options of the command) or if you just want to backup your image sitting on your ignite servers, you need to back it up with the backup software of your choice, from /opt/ignite/boot/name_of_your_image if you are using a recent enough version of the ignite_ux software.

hopefully this helps.

[Sundar_7]

1) I dont think this is possible. I know make_tape_recovery stores the archive in tar format. But I believe this is not the case with make_net_recovery archives.

2) You can boot your client from the IUX server using the boot command from the PDC

PDC> boot lan.AAA.BBB.CCC.DDD

AAA.BBB.CCC.DDD = IP address of the IUX server.

Remember, the IUX server and the client should be in the same physical network (broadcast domain) for this to work. If not, you need to configure a boot helper to act as a "mediator" between IUX server and the client

4) You can create a bootable archive by execting the following commands

in IUX server

# cd /var/opt/ignite/clients//recovery/latest

# make_medialif -f system_cfg -f archive_cfg -f control_cfg -l /var/tmp/lif1

# instl_adm -d -F /var/tmp/lif1 > /var/tmp/c

# vi /var/tmp/c
....
...
control_from_server=FALSE
run_ui=TRUE
#

# instl_adm -F /var/tmp/lif1 -f /var/tmp/c

# dd if=/var/tmp/lif1 of=/dev/rmt/0mn obs=2k

# cd /var/opt/ignite/recovery/archives//

# dd if=$PWD/ of=/dev/rmt/0mn obs=10k

[Vaish Raj]

Both client and ignite server are on same network.

Mel
----
You mentioned :

Make sure either your original system is offline or change the IP address of the new test system to prevent ip address conflicts. you can do this under system tab in the install interface.

I am bit not clear on this. You mentioned, original system. Is it the client machine(HP 11.0 )?

1)How about if i just boot the client machine(HP 11.0 )itself to make sure i can boot from archive.Hope this will not change anything on client. By doing this is it a fair indication that the archive is good and usable ?

2) When i created a archive i included complete vg00. I assume when i restore on client it creates complete vg00 ? Am i correct ? Is it advisable to add other mount points to archive ?

3) If i have to recover client(HP 11.0), i will restore Vg00 using ignite archive and then after restore other mount points from other backup. Any comments ?

Sundar
------
I am not clear on steps you mentioned for 4). If possible can you give brief idea what we are doing in each step.

I assume,once i create a boot tape, if required i can connect a local tape to client( HP 11.0) and boot the machine from this tape. Are my assumptions are correct ?

Thanks

[Vaish Raj]

Hi,

Any idea what print_manifest and how to make use of it.

Thanks

[Sundar_7]

Vaish,

Mel was suggesting that you should try to restore the network recovery archive to a test system that is of the same hardware model. This way you can confirm you are able to test the IUX archive.

So, in this case, if you are restoring your IUX network archive to a machine other than the IUX client, then once the restoration is complete, more than one system is going to have the same IP address.

That is why one of the system should be offline. This is not required if you are restoring the IUX archive to the same system that it is intended for.

1) Yes just booting the client will not break anything. But did you include -i option with make_net_recvoery. I never tried without -i option, but I believe without -i option, you will not be able to stop the restore ! just confirm before trying

2) Yes it creates complete VG00. By default IUX wipes off the entire disk included in the backup and restore it from the tape. Nope, it is not advisable to include any other data apart from VG00 in the recovery tape. Technically speaking, you can include , but not recommended.

3) In most cases you need not have to restore the mount points from backup. Say your IUX client root disk goes for a toss, you restore VG00 from the tape, it automatically imports all other Volume groups and mounts them when the restore is complete as long as the rest of the data vgs/disks are intact.

The step 4 are the steps needed to create a bootable tape off the make_net_recovery archive.

Boot tape contains 2 parts

1) Bootable LIF volume
2) Archive to restore from

You will have to execute the following commands from the IUX server.

# cd /var/opt/ignite/clients//recovery/latest

# make_medialif -f system_cfg -f archive_cfg -f control_cfg -l /var/tmp/lif1

make_medialif creates a LIF file based on the configuration files for the client

# instl_adm -d -F /var/tmp/lif1 > /var/tmp/c

# vi /var/tmp/c
....
...
control_from_server=FALSE
run_ui=TRUE
#

You dont want to control from the server. So you need to edit the configuration file and set the control_from_server to FALSE.

# instl_adm -F /var/tmp/lif1 -f /var/tmp/c

This command inserts the modified file back to the LIF volume

# dd if=/var/tmp/lif1 of=/dev/rmt/0mn obs=2k

Copy the LIF volume to the tape

# cd /var/opt/ignite/recovery/archives//

# dd if=$PWD/ of=/dev/rmt/0mn obs=10k

Copy the archive to the tape.

Now you have create a bootable tape

[Sundar_7 · Accepted solution]

print_manifest comes with Ignite-UX.

It is very useful to print the hardware and software information about your system.