VPLEX: How to VMotion between two VPLEX Local systems

VPLEX does not support XCOPY across independent VPLEX Clusters.
VPLEX would support XCOPY across two clusters but only in a Metro configuration. 

To resolve this issue:

1. Disable XCOPY on affected storage views on VPLEX.
2. Enable accelerated locking on ESXi hosts.

Workaround:

1. On the affected storage-views, disable XCOPY using the following commands.
   • Change directory (cd) to the affected storage-views and run the following command:

The storage-view should now have XCOPY disabled:

VPlexcli:/clusters/cluster-id/exports/storage-views/STORAGE-VIEW-NAME> ll
Name                      Value
------------------------  ------------------------------------------------------------------------
caw-enabled               true
controller-tag            -
initiators                [SV_D1, SV_D2]
operational-status        ok
.
.
.
virtual-volumes           [(0,DEV_0,VPD83T3:6000144000000010xxxxxxxx,3T),
                          (1,DEV_1,VPD83T3:6000144000000010xxxxxxxxxx,3T),
write-same-16-enabled     true
xcopy-enabled             false  <------------------------------

2. On the affected ESXi hosts, enable accelerated locking but disable accelerated move (XCOPY). 

Rather than disabling everything in VMware vStorage API Array Integration (VAAI), users can be selective and disable the unsupported primitive on the ESXi hosts.
To be more specific on the changes:

HardwareAcceleratedLocking = OK; enable (atomic test and set)
HardwareAcceleratedMove = Not OK; leave disabled (clone blocks, full copy, xcopy)
HardwareAcceleratedInit = OK; enable (zero blocks, write same)