Veeam quick migration for single vmdk

[HansA]

We have a VM (Server 2012R2 file server) with multiple disks, which we are migrating to new storage. All but one of the disks were able to be migrated using storage vMotion, but the last (~4TB) disk fails with an error about failing to unstun the VM for vMotion. VMware support states that the only option is to power off the VM and use WinSCP to manually copy the files to the new storage, which is not feasible as it is estimated to take far longer than we can get a maintenance window for. If we use Veeam quick migration for this, hos long can we expect Veeam to have the VM powered off for? Is it powered off only for the time it takes to move the state, or for however long it takes to copy the vmdk files? Is there a better way to get this last vmdk file migrated with minimal downtime?

[Vitaliy S.]

Hi Hans,

If you want to control this process and start the failover in the maintenance window, I would recommend using a replication job instead and then trigger a permanent failover operation at the required time.

Thanks!

[foggy]

Using planned failover could fit even better.