Cross vCenter vMotion fails when using snapshots LUNS as DR
search cancel

Cross vCenter vMotion fails when using snapshots LUNS as DR

book

Article ID: 400195

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

When using snapshot luns for across sites (snapshots of luns taken on site A and the snapshot is then force mounted on site B with no changes) Cross vCenter vMotion faild with message:

"Virtual machine VMName vim.VirtualMachine:########:vm-#### in Cluster#-cluster in VDCX-vdc failed to migrate"

 

/var/log/vmware/vpxd/vpxd.log reports the following:

error vpxd[38330] [Originator@6876 sub=VmProv opID=m83ad03x-######-auto-e4xa-h5:########-3e-01] xVC Host Migrate failed at vpx.vmprov.RegisterDestinationVm for poweredOff VM 'VM-Test' (vm-#####, ds:///vmfs/volumes/########-########-####-0025b512a008/Test/Test.vmx) on host-## (##.##.##.##.) in pool resgroup-9 with ds ds:///vmfs/volumes/########-########-####-0025b512a008/ to host-## (###.###.###.###) in pool resgroup-9 with ds ds:///vmfs/volumes/########-########-####-0025b512a008/ with migId 86470#####984171666 with fault vmodl.fault.InvalidArgument

 

Environment

vSphere 8.x

Cause

The IDs of the snapshot luns are identical to the IDs of the luns which were snpashotted

Due to this, the Cross vCenter vMotion fails as the vMotion process believes it is the source and destination datastores are the same

Resolution

Re-signature the snapshot luns before doing migration.

 

For steps how to do re-signaturing please see Troubleshooting LUNs detected as snapshot LUNs in vSphere