How do I troubleshoot VMDK File Not Found Errors?



The Datto device encounters VMDK file not found errors.


  • Agentless backups


Issue Symptoms

These errors are most commonly seen:

  • On pairing a server with the device
  • During the backup process, as shown below:
Backup Error at 10:31am Tuesday August 9th
Critical backup failure: VMDK file not found: /home/agents/vm-32-SuperreliableDC/vddk-fuse/SuperreliableDC.vmdk. Check if VM mount succeeded.


These failures apply to agentless backups, and can be caused by ESXi failing to resolve a VM's address by hostname. Finding the VM is the first step of the backup process. The vddk-fuse process then mounts the snapshot from the VMWare environment for network transfer to the Datto device.

This error can also be caused by independent disks being attached to the VM. Independent disks are not affected by VMware snapshots, so the VMDK 'file not found' error can occur during pairing.


To resolve this error, make sure that there is an internal DNS entry on the Configure → Networking tab of the web UI, as shown in Figure 1.

Figure 1: Configure → Networking

Make sure  internal DNS entries are listed above the public entries, as shown in Figure 2:

Figure 2: Datto appliance with Server 1 and Server 2 set to internal DNS, and Server 3 set to public DNS

If you are still unable to pair the protected agent or resume backups, add the Datto device to your domain via the Configure → Networking tab of the GUI. Then, test communication to the target VM again. This step only allows you to confirm that internal DNS troubleshooting is necessary; you should not leave the device on the domain after troubleshooting.

Was this article helpful?

0 out of 0 found this helpful

You must sign in before voting on this article.

Calling all Partners! We want to hear your feedback! Please participate in this quick survey and help us build a better, more-relevant Knowledge Base!

Want to talk about it? Head on over to our Community Forum!