VPlex: How to vmotion between two VPlex Locals
Summary: This KB article outlines how to migrate between two VPlex Local systems
Instructions
VPLEX would support XCopy across two clusters but only in a Metro configuration.
To resolve this issue:
- Disable XCopy on affected storage views on VPLEX.
- Enable accelerated locking on ESXi hosts.
Workaround:
- On the affected Storage-views, disable XCopy using the following commands.
- Change directory (cd) to the affected storage-views and execute the following command:
The storage-view should now have x-copy 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 <------------------------------
- On the affected ESXi Host(s), enable accelerated locking but disable accelerated move (XCOPY).
Rather than disabling everything in VAAI, the user can be selective and disable the unsupported primitive on the ESXi Host(s).
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)