make_tape_recovery restore to smaller disk drive

[John Knapp]

I have a K570 running HP/UX v10.20 and it boots off of an older Symmetrix 3930 array that is soon to be retired. The boot drive 8/12.0.0 is 11.6GBs. So I have to migrate vgroot from the Symm to (hopefully) an internal Seagate 8.7GB drive (10/0.5.0 Unused) ... I plan to use M_T_R (A.3.6.82)to "clone" the vgroot to the Seagate drive and have some questions:

Can you "clone" a vgroot to a smaller drive by ... say reducing the size of your swap devices during the interactive recovery process ? ... 90% of my physical extents in the VG are allocated.

Do you HAVE to boot up from the M_T_R tape in order to create the alternate boot device or can you "clone" the target drive in multi-user mode ?


root@ocr_hpux: / >
# vgdisplay vgroot
--- Volume groups ---
VG Name /dev/vgroot
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 8
Open LV 8
Max PV 16
Cur PV 1
Act PV 1
Max PE per PV 2958
VGDA 2
PE Size (Mbytes) 16
Total PE 737
Alloc PE 665
Free PE 72
Total PVG 0

There is no plan to upgrade HP/UX or IUX.

[John Waller · Accepted solution]

Hi John

In answer to your questions.

If I'm understanding correctly you wish to re-install your O/S from a make_recovery_tape image to a smaller disk on the same server.

You have already answered your second question by the fact that you have said you will need to change the sizes of lvols during the interactive recovery process. You only get to that stage by booting from a bootable tape/cd.

With regards to using a smaller disk, that shouldn't be a problem. One thing you will need watch is when you start the install, you will need to make sure vg00 does NOT include the existing disk. By default your make_recovery_tape will install back to the original disks but this can be easily changed during the install process.

As well as reducing swap space you may be able to make /stand /tmp /root /home smaller if you have unused space within these file systems.

[Steven E. Protter]

Shalom,

You can do a whole disk copy with dd and then the normal preparation of a disk for booting. Problem is you have less pace so you must plan precisely.

The answer to your actual question is no.I do not believe this plan will work.

Since Ignite is free you can do make_tape_recovery, or make_net_recovery and then manually intervene in the recovery process to set up smaller filesystems.

The liklihood of trouble is high and you may lose the system. If you are careful though Ignite is the way to go. If you want to have a good chance of trying this only once.

SEP

[Carlos Fernandez Riera]

If you had purcased MIRROR-UX the best way is add new disk to vg00 and mirror each lvol

You can add more than one disk , even if they are of different size.

You will find full description of process in HP LVM Adminstration guides.

2- yes you can use Ignite to recover and resize your FS. At least your filesystems are at 100%, you only need the size reported as used running bdf command, plus swap.

If you dont have more disks that the internal the problem is reduce data ( removing, compressing)