VMware — failed to create snapshot during snapshot creation
failed to create snapshot during snapshot creationfailed to create backup during snapshot creationMatched case-insensitively — AWS wraps these phrases in longer messages that vary by resource type.
What is actually happening
AWS Backup could not get VMware to take a snapshot of the VM. AWS attributes this to a problem on the VMware host where the Backup Gateway appliance runs — but in practice it is just as often the VM's own host, the datastore, or a failed quiesce. A common cause is VMware being unable to quiesce the guest, which shows in vCenter events at the exact backup time even though the AWS error says nothing about it.
How to fix it
- Identify which ESXi host runs the AWS Backup Gateway appliance, and check that host's health first.
- Check the datastore holding the VM: free space, accessibility, and storage latency or errors.
- Open vCenter events filtered to the exact backup timestamp — quiesce failures and snapshot consolidation problems appear there, not in the AWS message.
- Try creating a snapshot of the VM manually in vSphere. If that fails too, the problem is VMware's, not AWS Backup's.
- Check for existing unconsolidated snapshots on the VM and consolidate them.
- Verify the ESXi host's connectivity to vCenter and to the datastore.
What AWS documents
AWS gives the possible cause as an issue with the VMware host where the gateway appliance resides, and directs you to review that host's configuration.
Source: AWS Backup Developer Guide — Troubleshoot VM issues (Aborted backup job)
Stop finding this one failure at a time
BackupLens watches every AWS Backup job across every region, matches each failure against this catalogue automatically, and sends you the cause and the fix — instead of a job list you have to read line by line at 3am.
Start free trial