I'm looking to implement storage vMotion in vSphere and wanted to try to clarify a few of the requirements. In 3.5, VMs with snapshots could not be SVM'ed. Has this changed now by 4.1 or does anyone know if it is going to change in future? Has anyone found a workaround for this limitation?
Thanks
There is currently no workaround for this. The only way is to commit snapshots and then svMotion them over. Who knows what the next major release will bring to the table though!
If you found this at all helpful please award points by using the correct or helpful buttons! Thanks!
No, it has not changed, you cannot storage vMotion a VM with active snapshot. vSphere 5 is coming next year, but I do not know if it has any improvements for this.
Tomi
Hi
According to the Data Center Admin Guide "Virtual machines with snapshots cannot be migrated using Storage vMotion." check page 214 at
Its a best practice to commit all snapshots before you do a storage vmotion since there are two processes that are running simultaneously, just like when you do a CUT and PASTE
SvMotion might work just fine at time with snapshots but its not recommended.
If you found this or other information useful, please consider awarding points for "Correct" or "Helpful".
f-10
VCP3, VCP4, HPCP, HP UX CSA
There is currently no workaround for this. The only way is to commit snapshots and then svMotion them over. Who knows what the next major release will bring to the table though!
If you found this at all helpful please award points by using the correct or helpful buttons! Thanks!
We have been struggling with this one since VMware created SVM. Clients need to be able to SVM VMs with snaps to load balance storage and move VM's which have snapshots to free space as the datastores fill.
Since we operate a large dev/test setup, 80%+ of our VMs have snapshots and the users will not commit their snaps, lose all of their restore points, so we are in a bind constantly trying to move VMs w/ snaps to larger free space.
Even if we had to do that move with the VM powered off, as long as the snaps, permissions etc.. were maintained, that would be a good first step.
Please bump this to the top of any MUST HAVE list for a release sooner than later.
Thanks, GC Mobley
OK thanks for input
Even if there would be a workaround I wouldn't recommend it, trying to troubleshoot snapshots gone bad is not a lot of fun I can tell you that. Keep it simple and supported,
Duncan (VCDX)
Available now on Amazon: vSphere 4.1 HA and DRS technical deepdive