One thing that has not been mentioned so far is performance.
There is a performance hit on reading all of that data off one Datastore and for writing it on another data store. I suspect there will be SCSI reservations as it grows the VMDK file as it comes in, unless it preallocates and then backfills. SCSI reservations are over dramatized but this may be a legitimate case.
Not the question is does the performance hit matter? That is an operational issue not a technical one. Thats why some environments only do Storage VMotion in a maintenance window or out of ours. Others do it at any time. Just because you can do it, does not always mean you should.
Just something to consider in your decision making.
Rodos
Consider the use of the helpful or correct buttons to award points.
Blog: http://rodos.haywood.org/
Rodos
{size:10px}{color:gray}Consider the use of the helpful or correct buttons to award points.
Blog: http://rodos.haywood.org/{color}{size}
