1833137 Members
3463 Online
110051 Solutions
New Discussion

Cloning system problem .

 
Lim_2
Occasional Advisor

Cloning system problem .

Hi , I have problem on cloning system .
2 servers , both servers are L2000 , differeces
are processor speed and disk size ( original server : 9GB disk , new server : 18 GB ).

Original server is running kiwiplan software .
I have tried the following method but unsuccesful :

1. Install Ignite Ux using sept 2001 media ,
do a make_recovery -Av on original server
and did recover on new server .
Result not satisfied as every logical volume
size are less ( small ) than original server
Should be pax command unable to handle
files size more than 2Gb .

2. Fresh install os on new server .
Did a full fbackup on original server
excluded few files ( /dev , /etc/ioconfig ,
/etc/lvmtab ...) and restore to new server .
Unsatisfied result also as the size
of /usr1 which is having the kiwiplan
software is still less than original server
and the software is not able to run .

Question : Why fbackup not able to backup all
the files ?
Fbackup did in single user mode and
kiwiplan software is not running .

3. Thinking to user dd to clone the disk but
the current volume group config on original
server only able to recognize 10 GB .

Pls advice how can i clone the original server
to new server .
TQ .

10 REPLIES 10
ian Dennison
Regular Advisor

Re: Cloning system problem .

Did you specify a default Ignite recovery, or did you use the menus to modify the logical volumes used?

I cannot remember the name of the menu option offhand, but you can alter the logical volume sizes that are used before beginning the recovery.

Cheers, Ian Dennison
Lets do it to them before they do it to us! www.fred.net.nz
Ruediger Noack
Valued Contributor

Re: Cloning system problem .

Hi Lim,

use your Ignite tape to set up your new server.
In the configuration part of installing you have to choose the option to modify lvol size.

Good luck
Ruediger
Lim_2
Occasional Advisor

Re: Cloning system problem .

Hi , tq for the replied and sorry if i didn't specify more detail on item 1 .
Every logical volume size are same
to the original server logical size .
The problem is every logical volume total used size are less than the original server =meaning
not all files are archived during the make
recovery process .
I think it should be pax command that is not
able to backup files that are more than 2 GB .
James R. Ferguson
Acclaimed Contributor

Re: Cloning system problem .

Hi:

Two suggestions. First, use the latest Ignite software and its 'make_tape_recovery' (which supersedes the old 'make_recovery'):

# make_tape_recovery -x inc_entire=vg00 -I -v -a /dev/rmt/0mn

The '-I' option of 'make_tape_recovery' is the *same* as the '-i' option of the old 'make_recovery'. '-I' causes the Ignite process to be interactive when booting from tape.

Secondly, I suspect that your problem may be related to this. When you use the advanced installation option to select logical volume sizes, I have seen cases where *some* of the volumes are offered for *fixed* sizing and some are offered for a percentage. Make sure that you specify the sizes of logical volumes that you need/want.

For current Ignite software, go to:

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

Regards!

...JRF...
Lim_2
Occasional Advisor

Re: Cloning system problem .

Hi , i have all the logical volume sizes same as the original server after i did the make
recovery on new server .
Meaning original server
/ 150MB
/home 100MB
/usr 800MB
/var 1024MB
/usr1 5000MB
....
I got back the settings and the make recovery is good enough to detect the 18 GB disk .
The problem is that the total used sizes on each logical volume is less than the original server.


tq.

Ruediger Noack
Valued Contributor

Re: Cloning system problem .

Is there also a diff if you compare the du output. May be there are different block size in the VG

Ruediger
Lim_2
Occasional Advisor

Re: Cloning system problem .

Hi , I am using bdf command to compare . My customer main concern was their kiwiplan software , according to the kiwiplan vendor , if all files are copied to the new server ,the software will be able to run .
kiwiplan is reside in /usr1 and total used size for /usr1 is less than original server if i am using Ignite.

TQ .
James R. Ferguson
Acclaimed Contributor

Re: Cloning system problem .

Hi again:

As far as 'pax' goes, its limitation is that no *individual* file can exceed 2GB. Otherwise, Ignite would use multiple tapes as required.

When you say sizes are less, how much? Remember that the size of a directory grows as files are added beneath. However, simply removing files does not return the space. Recreating (as Ignite recovery would) "recovers" the space and you will see the new directory size as much smaller.

Regards!

...JRF...
Lim_2
Occasional Advisor

Re: Cloning system problem .

Hi , the /usr1 is less few hundred MB and each os logical volume are less about few MB .

TQ.
Helen French
Honored Contributor

Re: Cloning system problem .