Home / AWS Backup errors

VMware — abort signal detected

Critical ABORTED AWS Backup
What AWS reports
abort signal detected

Matched case-insensitively — AWS wraps these phrases in longer messages that vary by resource type.

What is actually happening

Three documented causes, all of which end the same way: insufficient network bandwidth, too few backup gateways for the number of VMs, or a completion window too short for the data volume. The job runs out of time and is aborted.

How to fix it

  1. Confirm you have at least 100 Mbps upload bandwidth to AWS — below that, the gateway cannot complete any backup or restore job at all.
  2. Check whether a bandwidth rate limit is configured on the backup gateway and raise it if so.
  3. Add gateways if more than four VMs need to run concurrently.
  4. Increase the Complete within duration in the backup plan.

What AWS documents

AWS lists low bandwidth, too few gateways and an undersized completion window as the causes, and states 100 Mbps is the minimum for the gateway to function.

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