-
- Service Provider
- Posts: 14
- Liked: never
- Joined: Apr 15, 2016 2:45 pm
- Full Name: Hans Ashman
- Contact:
Veeam quick migration for single vmdk
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?
-
- VP, Product Management
- Posts: 27112
- Liked: 2719 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: Veeam quick migration for single vmdk
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!
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!
-
- Veeam Software
- Posts: 21070
- Liked: 2115 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Veeam quick migration for single vmdk
Using planned failover could fit even better.
Who is online
Users browsing this forum: Bing [Bot] and 39 guests