VMware ESX Backup fails with fault detail “FileFaultFault”
This article helps you resolve the VMware ESX backup failure with fault detail FileFaultFault Issue Symptom FAILURE DUMP SUMMARY: 127.0.0.1...
FAILURE DUMP SUMMARY: 127.0.0.1 "\esx-hostnamedatastorevm-name" lev 0 FAILED [missing size line from sendbackup]
missing size line from sendbackup” in the FAILURE DUMP SUMMARY for VMware ESX backups.FAILED DUMP DETAILS, you see “A file was not found”, as in the example below:FAILED DUMP DETAILS: /-- 127.0.0.1 "\\esx-hostname\datastore\vm-name" lev 0 FAILED [missing size line from sendbackup] [...snip...] ? stdout: Error: [amvmware-disk-helper.cc:154] 4 A file was not found
“A file was not found” generally occurs when the guest OS is running Windows and the disk.EnabledUUID VM parameter is set to true. To resolve this, please use the following procedure in a vSphere client:
disk.EnableUUID from true to falseChanging this value changes the backup from an application-consistent backup to a crash-consistent backup. However, this is the only known way to resolve the issue.
Contact us for a free 30-minute consultation and learn how our fully managed solution can protect your business and streamline your operations. Get started with Zmanda Pro today!
Book a meeting