VM Quick migration btn vCenter Error

[fsseremba]

Support case ID: 01756773
Please help, i'm getting the following error messages when i try to migrate a VM from once vCenter to another vCenter;

Code: Select all

4/7/2016 7:53:01 AM :: Copying VM files Error: VDDK error: 16000 (One of the parameters supplied is invalid). Value: 0x003e803e00003e80
Failed to write to a virtual disk
Failed to replicate content of the disk [vddk://<vddkConnSpec><viConn name="158.XXX.XX.1" authdPort="443" vicPort="443" /><vmxPath vmRef="vm-244570" datacenterRef="datacenter-2" datacenterInventoryPath="XXHQ-3XX" snapshotRef="snapshot-395497" datastoreName="3XX_PRD_02" path="UXXXXBR001/UXXXXBR001.vmx" /><vmdkPath datastoreName="3XX_PRD_02" path="UXXXXBR001/UXXX 
4/7/2016 7:53:02 AM :: Hard disk 1 (50.0 GB) 1.0 MB read at 1 MB/s
4/7/2016 7:53:24 AM :: Failed to process VM UXXXXBR001 at 2016-04-07T075324 Error: VDDK error: 16000 (One of the parameters supplied is invalid). Value: 0x003e803e00003e80
Failed to write to a virtual disk
Failed to replicate content of the disk [vddk://<vddkConnSpec><viConn name="158.XXX.XX.1" authdPort="443" vicPort="443" /><vmxPath vmRef="vm-244570" datacenterRef="datacenter-2" datacenterInventoryPath="XXHQ-3XX" snapshotRef="snapshot-395497" datastoreName="3XX_PRD_02" path="UXXXXBR001/UXXXXBR001.vmx" /><vmdkPath datastoreNam

[PTide]

Hi,

Have you changed disk size recently by any chance?

[fsseremba]

Hi,
No disk size changed recently

[PTide]

Such an error might also occur when proxy is using direct-SAN access mode. If you're using a direct SAN mode please make sure that the proxy server on the target host side has a write access on the LUNs that is presented to it or use a different transport mode as support engineer has already suggested.

Thank you.

[fsseremba]

That's correct, i have been using proxy with direct SAN access mode but after changing the mode to network, I was able to migrate the VM across vCenter. Although it seems not to be a good solution to use in migrating more than 100 VMs with minimal disruptions. Any idea? Will replication using planned fail-over help? I'm trying to find a solution to use in migrating more than 100 VMs with minimal disruption or no downtime.

[foggy]

Consider using hotadd to populate VM data on target, this should provide performance comparable to direct SAN. Replication with planned failover is also a way to go if minimum downtime is required.

[PTide]

Will replication using planned fail-over help?

It won't help because during planned failover proxy servers are still used as an data movers thus your target proxy still has to have a write access to the target storage. Also planned failover process triggers the replication job to perform an incremental replication run which cannot be performed with direct-SAN access (VBR uses the Direct SAN access transport mode to read and write VM data only during the first session of the replication job.)

Thank you.