1 person found this helpful
This issue can occur if the vmfs volume containing the vmdk file of a virtual machine is on an NFS datastore and the datastore is mounted differently on both the source and destination machines. For example, if the NFS datastore on the source machine is mounted using IP and the destination machine has the datastore mounted using FQDN.
To check if the NFS datastores are mounted differently:
- Connect to the ESXi/ESX host using a remote KVM, direct console access, or using SSH.
- Run this command on both machines to check the NFS mount values:
On ESXi 5.x, run, esxcli storage nfs list
- Compare the output from both machines and check for differences. For example:
Output of command on ESXi/ESX host 1:
exit15_ISOs is /vol/vol0/home/ISO-Images/vol1 from fxit15.eng.vmware.com mounted
Output of command on ESXi/ESX host 2:
exit15_ISOs is /vol/vol0/home/ISO-Images/vol1 from 10.17.4.21 mounted
In these outputs host1 has the NFS datastore mounted using the IP address at 10.17.4.21 and the host2 has the datastore mounted using DNS name at fxit15.eng.vmware.com.
- Use the same mounting method on both machines. Either use the same IP address or use the same DNS name on both machines.
But The issue has been resolved,
I un-mounted the datstore from ESX host and mount it back with right folder name and path,
when we mounted initially we have mounted with wrong folder name,
example: \esx_ds01 in some of the ESX host and esx_ds01 in some of the esx host,
now I mounted back with esx_ds01 in all esx host and everything looks fine
Thanks a lot for your help Guyz