I have to migrate data from 10.20 to 11.0 on other system.

[pap]

I have a K220 existing server on hich lots of applications are running. The hp 6000 disk drives are connected to it.

I have to migrate everything on to other system K360 running 11.0. Can anybody guide me so that I have a safe migration. K360 is a fresh machine and I have installed 11.0 on it. I know that by exporting volume groups from old sytem and importing to new system will serve the purpose.Just to be on safer side, I am asking this question.


Thanks,

-Piyush.

[James R. Ferguson · Accepted solution]

Hi:

Use the 'mapfile' option of 'vgexport'. This allows the 'vgimport' to create logical volume devices files under the vg_name directory using the naming convention given in mapfile as opposed to the default naming convention used by the 'lvcreate'.

In total, you'll do something like this:

On old server:

# vgchange -a n
# vgexport -s -p -m /tmp/lvmconf_vgNN.map /dev/vgNN

On new server:

# mkdir /dev/vgNN
# mknmod /dev/vgNN/group c 64 0xNN0000
# vgimport -v -s -m /tmp/lvmconf_vgNN.map /dev/vgNN
# vgchange -a y /dev/vgNN

Regards!

...JRF...

[harry d brown jr]

To be on the safe side, BACKUP your data TWICE (at least) before "migrating" disks to other machine. Now once you have, you might want to upgrade the JFS versions of your data.

live free or die
harry

[Helen French]

Hi Piyush,

There are some stuffs you need to take care:

1) Take one ( or two) good full backup of the system, before doing any changes.
2) Make use of the mapfile option ( see man vgexport), if you are not using a standard naming convention ( lvol1, lvol2..etc).
3) Take a look at the /etc/fstab on the old server for checking any specific mount options.
4) Print out the VG information of all disks ( vgdisplay -v, pvdisplay and lvdisplay)
5) Make sure that you have the proper drivers installed on the new system for identifying your disk array/disks.

HTH,
Shiju

[pap]

Thanks Harry and James,

I think it is good to keep a copy of some important files like /etc/password, hosts.....etc.....

I am just keeping a back up of this files in case later it is needed. Please be advince if anything else is needed.

Thanks,
-Piyush.

[Sanjay_6]

Hi Piyush,

When you do a vgimport of the exported map file from the old server to the new server, make sure the device address are same. for eg, if the disk in the vg is cxtydz on the old server, the same disk should be seen as cxtydz on the new server. If such is the case, you can very easily do a vgexport to a map file on the old server, connect the disks to the new servers and do a vgimport using the map file. If the disk device files gets changed then you have to define the new device file in the vgimport command. Do a "man vgimport" for more help.

Hope this helps.

Regds

[balu_1]

Hi,

Few more tips to add:-

a) Identify customed made startup/shutdown scripts like scripts starts/shuts down database, security tools, etc during system reboots. You may have to copy and link them appropriate rc levels.

b) I would recommend to copy all config files under /etc like /etc/fstab, /etc/passwd, /etc/group, /etc/SHLIB, /etc/MANPATH, /etc/PATH, /etc/profile, /.profile, /etc/hosts, /etc/hosts.equiv, /.rhosts, /etc/inetd.conf, /var/adm/inted.sec, /etc/securetty, etc.

c) If your existing system is trusted then you may have to restore /tcb directory.

d)You have create a table of disks and its vg using hardware path. So that will be helpful for you import in new system. Try thorough SAM should display in hardware path.

Let me know if you have any more questions.

[pap]

Hi,
What should I do for Vg00 volume group?
How can I import it in a new system while migration.

[James R. Ferguson]

Hi:

In answer to your last question regarding vg00 on the "old" server: If you want to collect any files for comparison or use as a template, then copy them to the "new" server via 'ftp', 'rcp', 'tar', 'fbackup'). You do not indicate whether or not the "old" and "new" server's are the same OS level so be very selective and careful what you take.

Regards!

...JRF...

[pap]

Old system is HP-UX 10.20 on K220
New System is HP-UX 11.0 on K360

Once more question, once I export the volume groups from Old sytem with map file option, do I need to copy those mapfiles to new system? I mean can I directly export and Import volume groups to new system without copying mapfiles previously created?

[Helen French]

Hi Piyush,

You have to copy those map files to the new system inorder to import it using the same mapfile. Once you have done the vgexport, use ftp to copy those mapfiles to the new server.

HTH,
Shiju

[James R. Ferguson]

Hi (again):

Yes, you will need to copy the mapfiles from the 'vgexport' from the old to the new system before you can use them on the new system with the 'vgimport'. Since your old and new systems are different OS versions, I'd collect any configuration files you want for comparative or template purposes into a directory name of your choosing. Copy that directory to the new server and on a case-by-case basis, compare and/or update the new server's configuration files. In some cases, you will find improved documentation in 11.x although your local changes can be implemented directly. The number of files in the standard filesystems comprising vg00 on your new server that will require customization is relatively small and many will already be in the form in which you want them -- hence my suggestion to copy the old server's files into a reference directory of your choice.

Regards!

...JRF...

[Helen French]

Hi Piyush,

Again, for the vg00 (root vg), the best option is to keep printouts of all your config files needed. You can copy the config files to the new server too. Keep it in a temperary location and then you can make use of it. Do not directly copy those files to the new system as there is a version difference.

Another option is to do an NFS mount. You can mount the specific directories in the new server after exporting it from the old one.

Also if you really need to import the vg00 on the new server, you can do that also. Create a new VGname ( unused) using 'mknod' and import it manually. For doing this you should have the vgdisplay information:

vgimport /dev/vgxx physical_vol1 physical_vol2 ..

HTH,
Shiju