VMware — no gateways available to work on job
What AWS reports
no gateway available to workno gateways availableMatched case-insensitively — AWS wraps these phrases in longer messages that vary by resource type.
What is actually happening
Every backup gateway processes a maximum of four concurrent backup or restore jobs. Additional jobs queue and wait. If the backup start window passes while they are still waiting, they fail outright.
How to fix it
- Count how many VMs are scheduled in the same window and divide by four — that is the number of gateways you need at minimum.
- Deploy additional backup gateways to raise concurrency.
- Increase the Complete within duration on the backup plan so queued jobs still have time to start.
- Stagger VM schedules rather than starting every VM at once.
What AWS documents
AWS documents a limit of four concurrent jobs per backup gateway, with additional jobs queuing until the start window passes.
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