Quick migration...not following your directions ?

[EBoucq]

Hi,

Has anyone ever encountered that problem when you want to run a quick migration of a vm and Veeam doesn't take into account one of the datastores you pick as a destination and put the files into another one ?
It is very strange because there's no sign of that datastore in the logs...like I didn't even choose it !

Thanks.
Eric

[foggy]

Eric, we're unaware of such behavior, so please continue to investigate this with technical support. Thanks.

[Vitaliy S.]

Eric, did you specify cluster or a standalone host as your destination target?

[EBoucq]

Vitaliy,

the destination target is a host in a cluster.

Eric

[Vitaliy S.]

Do you migrate the entire VM to the datastore or specify different datastores for virtual disks?

[EBoucq]

the VM has 3 datastores. I'll call them A, B & C. The destination cluster has datastores D, E and F.
Here is Quick Migration behavior in 2 scenarios:

1°) I set up Quick Migration for: A --> D B --> E C --> F It does A --> D B --> D C --> F

2°) I set up Quick Migration for: A --> E B --> E C --> F It does A --> E B --> E C --> F

I checked:
- storage array zoning : all volumes have unique LUN id
- The datastore E (that one Veeam seems not to see in scenatio 1) is very big: 16 TB
- no error what so ever in the Veeam log but no mention at all of datastore E in the log files when I do scenario 1

[Vitaliy S.]

Does this happen for all VMs? Can you do a quick check with any dummy VM and see if this issue reproduces or not? If it is reproduce-able, then continue working with our support team.

[EBoucq]

This issue happens with any VM unfortunately....I'll contact the support team if I don't find anything soon...

Thank you Vitaliy.