Migration Server + EMC SAN

[I J Clifford]

Hi all - I have responsibility for building new server and SAN in new country based upon EMC SRDF duplication fromm one country to the other. It will be a track for track duplication of EMC (original) to EMC (target)

I'll be using Ignite to build new replacement server. Both old and new servers have primary and alternate links to the SAN in their respective country.

If I vgexport from original server to *.map file and then use vgimport on new server will this be sufficient to populate new /etc/lvmtab file in a sane fashion having created the group files /dev/*/group files in advance ?

Man page for vgimport "since the -s option causes a search on the system for each disks with the same vg_id. When vgimport reconstruct the newly imported volume group entry in /etc/lvmtab file, the order of disks could be different than it was before" -

so bang goes my load balance over 2 disk paths !

Or .... would I be better off with vgscan on the new server ?, perhaps with the -a option ?

All comments on this appreciated please.

Many thanks.

IJC

[Geoff Wild]

EMC Powerpath will take care of the load balancing.

Now, if you don't want to pay for that, then yes, you will have to "manually" load balance. When you do a vgimport - it takes the first path for all disks, and the alternate will be the second path - then you can vgreduce half the disks out then back in - and you will then have your "manual" load balance.

Rgds...Geoff

[I J Clifford]

HI Geoff thanks for the input.

Not sure about powerpath/licensing, I'll presume I'll manually balance as you mentioned.

When I get the /dev disk ID's I'll vgreduce the pri path by 50% of the disks, (allowing the old alt path to become the pri path) then vgextend to make the old pri path the new alt path.

10 pts, cheers, IJC.

[I J Clifford]

As per prior entry - thanks Geoff.