pvmove

[Matrah]

Hi,
My system is running with MCSG
Can i use pvmove command even if my system is running ? or must i desactivate MCSG and then use pvmove ?

thanks for your replies.

[Santosh Nair_1]

No, you should be able to do the pvmove without affecting the application. However, since the VG information for this VG will be changed, its best to do a vgexport from this machine after the pvmove and then vgimport the new map files onto the other nodes in the cluster.

-Santosh

[David Navarro]

Remember that new disks, must be accesible by others hosts in cluster.

[Stefan Farrelly]

If your pvmoving to a new disk youve added to a VG which is in an MCSG package then yes, at some point you will need to deactivate MCSG and export the VG and reimport it on the other SG node so it also knows about the new disk.

But actually doing the pvmove, you can do online anytime, no need to deactivate MCSG. But for the SG failover to work you may need to do the above.

[Stephen Doud · Accepted solution]

There should be no reason to halt the cluster throughout the 'pvmove' process.

/etc/lvmtab contains the list of disks for each VG. Should you desire to remove a disk from a VG, it can be done while the package is up using a vgreduce command.

If you have added a disk to a VG on one server, the other server's lvmtab can be updated without halting the cluster by merely vgexporting and vgimporting the volume group there (use a map file that contains the VGID to ease the process. VGID is loaded in the map file using the -s option of vgexport)

[Vitaliy Kushenrov]

You can not use pvmove if VG activated in shared mode.