Easy way to clone a server with distributed

[Peter Klausner_1]

Hi,

i want to clone a server A Class Sewrver which has distributed extents because i combined striping and mirroring.

I wanted to clone the server with an ignite tape but make_tape_recovery neither support distributed extents nor mirroring.

Who has any idea ?

Thanks in advance

[Frederic Sevestre]

Hi,

I guess the OS LV are not distributed.
On your source server you should create a make_recovery tape only for the OS, and backup the LV's data using fbackup (or tar, cpio..)on an other tape

Then restore the OS on the new server using the make_recovery, create the distributed LV and retore your data's tape on it.

Fr??d??ric

[Stefan Farrelly]

Frederic is completely correct.

Use make_recovery to make an image (almost) copy of vg00 on your new sever, then add into it your other non-VG00 volume groups and stripe+mirror them they way you want them setup, then use a normal backup to restore your non-VG00 volume groups.
This is the best way to do this as no other backup/clone method witll restore your striping+mirroring setup.

[Peter Klausner_1]

Thanks for the answers.
but i created all LV with distributed extents, expect of dump/swap
root and boot. They have to be contigous.

Still any idea ?

[Satish Y]

Peter,

I am not sure about mirrors, but u can backup non root VG, follow the steps,

# make_recovery -Apd /dev/rmt/0m

It will create /var/opt/ignite/recovery/arch.include file, u need to append the file by including all files and directory trees from filesystems from non root VG, e.g. if u have one filesystem called /testfs on non root VG, which u want to include into ur ignite backup, then run,

# find /testfs -print >> /var/opt/ignite/recovery/arch.include

repeat above for all filesystems u wwant to include. Then run recovery in resume mode,

# make_recovery -rCvd /dev/rmt/0m

DON'T use option "-A" in above cmd, it will over write "arch.include" file.

Ofcourse, if mirrors r not crated, u can create mirrors manually using lvchange commad.

Hope this helps u.......

Cheers...
Satish.

[Satish Y]

Sorry, one correction, use "/dev/rmt/omn"(non rewind tape) in all commands....

Cheers...
Satish.

[Tim D Fulford]

Peter.

Ignite does say that it will not recreate mirroring etc. However, the way I get 'round this is

1 - get ignite image of vg00 from source server, which is usually on 1 (mirrored pair) disk.
# make_tape_recovery ???vI ???x inc_entire=vg00 -a /dev/rmt/0mn

2 - boot from this tape & do an Ingite-UX restore of vg00

3 - Mirror up vg00 on target server, put on diagnostics & AUTO file...

4 - Create all the other application/data volume groups & logical volumes on the target system. Do this as you would like them (In your case, using extent based stripe & mirror). Mount any filesystems from these VG's

5 - fbackup/tar/whatever from source system all the remaining vg's & lv's data (not vg00, as you already have this).

6 - frecover/tar/whatever the data to the target system, which has the correct layout now.


** It may be tempting to do a full Ignite-UX image of the system & delete the filesystems in the menus, then set up system & use pax to extract the data from the Ignite-UX tape. Nice idea, saves doing two different backups, but DO NOT DO THIS, the filesystems will be deleted on the target system but it will still restore ALL the data on the Ignite-UX tape. It will fill up vg00 filesystems with your application data. Here speaks the voice of 3 days experience & lots of head scratching!!

Cheers

Tim