I read the man on pvmove and it looks very cool, especially the "auto-continue" if there is some sort of system interruption. I plan to try this on a new, non-production machine I am building out, but need to do something right now on the Windows LV.
BUT, according to 'man pvmove' it doesn't have a switch to leave a copy behind, or the old extents in place for a fallback. That makes me a little apprehensive about having something ready to roll back to in its most current "data" state. I don't think I am in the mood for this to be my first test case. haha. Feel's like a Murphy's Law morning. RedShift wrote: > Ben M. wrote: >> Using CentOS Xen current with the 5.4 update applied. >> >> I need to move a Windows 2008 installation in LVM2 from one pv/vg/lv to >> different disk pv/vg/lv. >> >> What are considered safe ways to move it on same machine and retain a >> copy until sure it reboots? >> >> Turn off (shutdown) in Xen create identical extents in target pv/vg/lv >> and mount -t ntfs and cp? dd? rsync? >> >> Or pvmove (doesn't look like it retains a copy)? >> >> Is there an equivalent to AIX cplv? >> >> > > > If you haven't created a volumegroup on the new target disks, add those disks > to the old volume group, execute pvmove on the old logical volume, when > that's complete, execute vgsplit to create the new volume group. Pvmove is > pretty robust, it can restart if it's been interrupted and can be aborted. > > > Glenn > _______________________________________________ > CentOS-virt mailing list > [email protected] > http://lists.centos.org/mailman/listinfo/centos-virt > _______________________________________________ CentOS-virt mailing list [email protected] http://lists.centos.org/mailman/listinfo/centos-virt
