Home / AWS Backup errors

EFS backup never runs — only one concurrent backup allowed

Warning EXPIRED AWS Backup
What AWS reports
a backup is already in progressbackup is already in progressanother backup is runningconcurrent backup limit

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

What is actually happening

An EFS file system allows only one backup at a time. A very large file system can take up to seven days to back up. If the schedule fires again while the previous run is still going, the new job simply queues — and if it is still queued when the backup window expires, no backup is created at all. The result is a file system that appears scheduled but silently produces nothing.

How to fix it

  1. Check how long the last successful EFS backup actually took before changing anything.
  2. Reduce the backup frequency for large file systems so a run can finish before the next one is due.
  3. Widen the Complete within window so a queued job still has time once the previous one ends.
  4. For very large file systems, consider whether daily backups are achievable at all, or whether a longer interval is more honest.

What AWS documents

AWS documents that only one concurrent backup can be queued per EFS file system, that very large file systems can take up to seven days, and that a queued backup produces nothing if the window expires.

Source: AWS Backup Developer Guide — Troubleshoot creating resources

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