CONTAP-478107: SnapMirror active Sync (SM-as) cross CG storage vMotion or clone using XCOPY results in failed VM
Issue
- Storage vMotion between SnapMirror active sync LUN’s/Datastore in same cluster peer consistency group ( CG ) results in VM crash
- VMware Clone deployment / vmkfstools between LUN in same SM-as relationship results in non bootable vmdk
- Using VAAI cloning and copy offload ( XCOPY) between primary LUN/ Vol and secondary LUN/ Vol additionally secondary to secondary replicas
Example:
Site A: storage vMotion from d1 ( primary replica ) to d2 ( secondary replica )
cluster1::*> lun show -vserver svm1_cluster1 -fields serial,serial-hex,zrto-status,zrto-vol-consensus
vserver path serial serial-hex *zrto-status zrto-vol-consensus*
------------- ---------------- ------------ ------------------------ ----------- ------------------
svm1_cluster1 /vol/d1/d1 weikD+W7xI9M 7765696b442b57377849394d *primary-in-sync true*
cluster1::*> lun show -vserver svm1_cluster1 -fields serial,serial-hex,zrto-status,zrto-vol-consensus
vserver path serial serial-hex *zrto-status zrto-vol-consensus*
------------- --------------- ------------ ------------------------ ----------------- ------------------
svm1_cluster2 /vol/d2_dest/d2 weikD+W7xzz1 7765696b442b5737784123456 *secondary-in-sync false*