different hardware paths

[Christopher Little_2]

I'm using Ignite to backup vg00 an N4000. vg00 is comprised of fibre attached disk. I'm going to be restoring to a different system than from which I performed the backup. It is almost a certainty that the hardware path for the fibre attached disk will be different on the new system. Is there a way to have ignite work in this scenario? Can one "fool" ignite into restoring down a differnt hardware path? Thanks for any help you can provide.

Chris

[Pete Randall]

The recent Ignite versions should handle this. You're presented with an Install interface, and can select the disks you wish to restore to.

Make sure you have the latest Ignite:

http://www.software.hp.com/products/IUX/index.html


Pete

[James R. Ferguson · Accepted solution]

Hi Chris:

This matters not. When you perform your Ignite recovery you will select the physical device(s) that you want to declare as volume group vg00. If you have created an Ignite recovery tape to include other non-vg00 volume groups, then the automatic restoration of those volume groups will fail because matching device files will not be present.

Regards!

...JRF...

[Christopher Little_2]

Thanks for the information. In regards to non-vg00 volume groups...Is there a way to restore them as well if they are on different hardware paths? I understand that an automated restore won't get it done but is there any sort of manual way to do it? Thanks.

Chris

[James R. Ferguson]

Hi (again) Chris:

Ignite recovery is really intended for the recovery of volume group vg00 and its contents. However, as you know, you can include other volume groups in whole or in part. That said, remember, too, that Ignite 'make_tape_recovery' uses 'pax' ('tar's superior cousin) to read and write data. Hence, you can extract anything you want from the Ignite tape by first skipping the bootable part of the tape and then extracting the archive:

# mt -t /dev/rmt/0mn fsf 1
# tar -xvf /dev/rmt/0m filename

Regards!

...JRF...

[Steven E. Protter]

If you've used make_tape_recovery or make_net_recvoery or a golden image with make_sys_image(used by the other two), you are all set.

When you boot the target server, you'll come into an interface that looks like the OS install screen. This will let you make adjustments to filesystem size, hardware path, networking and many other aspects of the clients eventual configuration.


If you are using an Ignite server, you can build a lot of that into a profile which will literally run by itself afer you initiate it from either server push or client pull.

Summary: You're all set. Make sure the target system is backed up and give it a try.

SEP