LVM - Migrating a nike array from 10.10 to 11.00

[Judy Traynor]

We are migrating from a K210 to a L2000. New disks were not purchased with the new system, so we will have to migrate our old nike internal array. We want to migrate without backup and restore(ing) the data. Does anyone know of a problem with this? We may only get one shot at it, so I want to be sure it works.

thanks.

[Robert Gamble]

Do a man page on 'vgimport'.

Use this cookbook to help make your plan:
1. mkdir /dev/vgXX
2. mknod /dev/vgXX/group c 64 0xXX0000
3. vgimport -v -m /$PATH/$MAP_FILE /dev/vgXX /dev/dsk/cXtXdX
4. vgchange -a y /dev/vgXX
5. vgcfgbackup vgXX

Good Luck!

[Paul Hite]

Also, I would make sure that I have installed the latest LVM patch on the 11.0 system before I did this.

[Shyam Kishore]

Hi,

As Mr.Robert Said the procedure will work fine. But it is not a good idea to go ahead without BACKUP.

-Shyam

[Dave Wherry]

The procedure Robert gave works fine. He left out one step though and there is one thing to watch for.
First, on your K210 you need to create the MAPFILE. When you look at the man pages for vgimport and vgexport that may have been obvious, just be aware of it.
When I did this, going from 10.20 to 11.0, the MAPFILE had an extra line in it that vgimport did not like. I don't remember what the line was, but, it was not a disk device. vgimport is looking to this file for a list of disk devices and choked on this extra line. I had to vi the MAPFILE and remove that line. Maybe it was a problem with the releases and patches I had. Be aware of it and check it.
The good news is it did no damage. The vgimport failed and I had to do it over.

[Dave Wherry]

Sorry, my mistake. The MAPFILE contains logical volume information not disk. You need to supply that on the command line.
Still, check for that extra line.