The vMotion failed because the destination host did not receive data from the source host on the vMotion network
2025-09-12T07:35:29.736Z cpu42:2097622)StorageApdHandlerEv: 110: Device or filesystem with identifier [naa.###############################] has entered the All Paths Down state.2025-11-04T04:20:07.215Z: [APDCorrlator] 365404863026us: [esx.problem.storage.apd.start] Device or filesystem with identifier [########-########] has entered the All Paths Down state.2025-11-04T04:20:07.215Z: [vmfsCorrelator] 365501040333us: [vob.vmfs.nfs.server.disconnect] Lost connection to the server #.#.#.# mount point /<mount-point>, mounted as #########-#########-0000-000000000000 ("<NFS_Datastore_Name>")VMware ESXi (All Versions)
The ESXi the VM is running on host has lost access to the datastore hosting the VM's files, so the vMotion eventually times out.
Engage SAN/NAS team and/or storage array vendor to investigate why the storage LUN's/Datastores have become inaccessible. See related KB: Storage device has entered the All Paths Down (APD) state
There are many issues that can result in similar vMotion errors. ESXi host networking issues/misconfiguration are also a common cause. If you do not observe the "All Paths Down state" errors in the vmkernel.log, as shown above, please see the following KB's for further troubleshooting: