VMware — upload failed or timed out during data ingestion
What AWS reports
failed to upload backup during data ingestioncloud network request timed outdata ingestionMatched case-insensitively — AWS wraps these phrases in longer messages that vary by resource type.
What is actually happening
The link between the VM environment and AWS is congested or too slow to carry the backup within its window. Required bandwidth depends on VM size, incremental change rate, backup window and restore requirements.
How to fix it
- Verify you have at least 100 Mbps upload bandwidth to AWS — this is the documented minimum for the gateway to function at all.
- With a large number of VMs, budget well above 100 Mbps; jobs still time out at the minimum when the estate is large.
- Check for a bandwidth throttle configured on the gateway itself.
- Reduce how many VMs back up simultaneously, or lengthen the window.
What AWS documents
AWS states 100 Mbps upload is the minimum for the gateway to complete any backup or restore, and that jobs may still fail above it with many VMs.
Source: AWS Backup Developer Guide — Troubleshoot VM issues
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