Thank you for responding, Hyper-v is still very new to us. I will attempt to clarify the mount points and mappings. All storage is in the same cDOT cluster.
I will be switching volume names to hv_2008. The base issue is still the same but with the hv_2012 conversion we received different errors that would complicate and distract from this issue.
VMware there are no qtrees in the VMware environment, all mount points are to volumes.
SVM_VM:/vm_2008 /vm_2008 -- All VMware vm’s are in there own directories.
Hyper-v mapping is a qtree created by VMM, we are using SMI-S provider to connect to VMM to create shares and mappings
\\SVM_HV\hv_2008 -- hv_2008 is a qtree on the filere /hyperv_2008/hv_2008
VMware to Hyper-v target, in the VMWare environment, both environments see the same path, hv_2008
SVM_VM:/hyperv_2008/vm_2008 /hv_2008 - (this may be the issue, I will attempt the mapping directly to the qtree not the /vol/qtree)
In VMware we storage vmotion the vm to the shared mapping /hv_2008
Conversion:
If we set the “Hyper-V destination path” to \\SVM_HV\hv_2008\ or to /hv_2008 we get this error message
This is a direct copy of the logs:
Error Description : ONTAP_DEST_PATH_INVALID
Error Reason : The destination path //SVM_HV/hv_2008/ is not on the same volume of the source VM (/hyperv_2008).
Error Fix : Correct the destination path on the ONTAP configuration and re-run again.
VMmigration succeeded when we changed the “Hyper-V destination path” to /hyperv_2008. However the VM guest did not start because it was on a file system that is not registered with VMM
This is a copy of the VMM error:
Error (13932)
The file \\SVM_HV\hyperv_2008\hyperv-w2k8ent-test\hyperv-w2k8ent-test.vhdx is in a share which is not registered to the cluster cDOT.co.local.
Recommended Action
Register the share to the cluster, and then try the operation again.