swap harddisk

[juno2]

I have two unix with diff. hardware conf. ( diff. class ) - UNIX A & B, cos the harddisk of UNIX A was corrupted , can I just swap the harddisk of UNIX B to UNIX A ? if i do so , is it bootable and run normally ? thx

[V.Tamilvanan]

Hi,
The internal hardware structure of different class servers varies. So whatever the device files,device drivers, kernel, Hardware path varies from one Class Server to other. So you cannot swap the root disks straight away.

My suggestion is you can try using ignite-UX to create image of Unix B on a tape and use that tape to build the Unix A after replacing Unix A
defective disk.

HTH

[Bill Hassell · Accepted solution]

Without additional information, the answer is no. The disk must be the same type of interface (not just SCSI, but type of I/O card). Additionally, if the class is significantly different (ie, an N-class and a V-class or D-class) then there is no hope for booting the disk from another system.

You definitely need to look at Ignite/UX to save and recover your bootable disk: http://www.software.hp.com/products/IUX/

[Sridhar Bhaskarla]

Hi,

If both are of different hardware, then you cannot use that boot disk.

However, it may work in different releases of the same hardware. Like N4000's boot disk on RP7400.

-Sri

[Sunil Sharma_1]

Hi,
if your hardware is not same it won't work.

but you can use ignite to do this task, latest ignite work across platforms..

Sunil

[juno2]

thx all reply, is it mean no no function like auto detect in windows ? except to use tools like ignite ,is there other simpler method to do that ?

[Sridhar Bhaskarla]

Hi,

No. There is no simple method to recover your system. At the best you can do is to install the latest version of ignite on UNIX B, create a make_tape_recovery tape and recover it on UNIX A system. Again, this is dependent on what kind of systems you have. Old servers like G,H,I etc are not supported.

-Sri

[juno2]

thx reply,

Actually my case like this , i have two HP server that running HPUX10.20 (D class) , one on remote site (UNIX A) , now that HD on the remote site can't be boot , ( but two HD volume size are not the same , UX A is 2G and UX B is 8G) , now the staff on the remote site has send me the HD ( only the HD) to recover.
With your mentioned method , Do you mean install ignite to UX B , and create make_tape_recovery tape , then recover it to the UX A .

[juno2]

thx all,

does ignite recover the whole system include the partition ? can i just recover one of the partition ? thx.

[Bill Hassell]

Are you are trying to recover the data on the disk from the remote site, or simply make a copy of your local system? Recovery will require a lot of technical resources (ie, consulting or training). As far as the term partition, this isn't clear. The bootable disk is (usually) volume group zero or vg00. The inability to boot may be due to hundreds of reasons, from hardware errors to configuration problems to accidental destruction of the boot area (and probably all vg00 data) with an incorrect dd command. So fixing a partition would not likely make the old disk useable.

But to simply clone (clopy) your local system to the unbootable disk, then making an Ignite/UX copy of your current vg00 (the bootable volume) will allow you to restore it back to the unbootable disk. The resultant disk will be bootable and run just like the local disk.

Well, here are the exceptions and issues to be resolved:

1. Since the remote disk is only 2Gb, it will fail if you have more than 2Gb of data on the local system. There are far too many questions about how to resolve that problem to be discussed here.

If you can figure out a way to restore the required logical volumes onto the 2Gb disk, then continue. Otherwise, put the (way too small) unbootable disk on the shelf and get an 8Gb disk as a replacement. Then use Ignite/UX to clone your local system

2. The clone is fine for the local system. However, you need to look at the I/O on the local system. Ignite/UX put everything back but this may not match your remote system. especially additional disks, tape drives, CDROM disk, LAN card(s), etc. You'll need an I/O map of the remote system to conifgure the differences.

This task is greatly simplified if you restore the Ignite/UX tape onto the disk inside the remote system. Ignite/UX will configure the local devices automatically when used on the actual system.

3. Once all the hardware has been configured and device file names checked to match any application programs that depend on the names, you'll need to configure any network differences for the remote system.