I'm guessing you are talking about hardware acceleration and the vaai copy, rather than T10, as T10 Is just for reclaiming space.
There are a lot of conditions for which need to be true for the copy to work using vaai, however if it fails to validate it should just fall back to the old skool method and use SCSI-2 reservations.
Worth checking these
VAAI hardware offload cannot be used when:
The source and destination VMFS volumes have different block sizes
The source file type is RDM and the destination file type is non-RDM (regular file)
The source VMDK type is eagerzeroedthick and the destination VMDK type is thin
The source or destination VMDK is any kind of sparse or hosted format
Cloning a virtual machine that has snapshots because this process involves consolidating the snapshots into the virtual disks of the target virtual machine.
The logical address and/or transfer length in the requested operation is not aligned to the minimum alignment required by the storage device (all datastores created with the vSphere Client are aligned automatically)
The VMFS datastore has multiple LUNs/extents spread across different arrays
Note:
Hardware cloning between arrays (even if within the same VMFS datastore) does not work.
For information on supportability with Horizon View, refer to KB Article View Composer API for Array Integration (VCAI) support in VMware Horizon View (2061611).
So if it tries and fails it will fall back anyway, and it shouldn't have any issue deterring they are different arrays.
Take a look at this kb too
http://kb.vmware.com/selfservice/micros ... Id=1021976