Another backup is already running for this resource
backup job failed because there was a running job for the same resourcerunning job for the same resourceconcurrent_jobMatched case-insensitively — AWS wraps these phrases in longer messages that vary by resource type.
What is actually happening
AWS Backup will not run two backup jobs against the same resource at once. A second job waits for the first to finish — and if the wait consumes its completion window, it expires without producing anything. The usual cause is two backup plans or two rules targeting the same resource, or a schedule firing again before the previous run has finished.
How to fix it
- In AWS Backup → Jobs, filter by RUNNING and find the other job against the same resource. From the CLI: aws backup list-backup-jobs --by-state RUNNING
- Check whether more than one backup plan or rule selects this resource — overlapping tag-based selections are the usual culprit.
- If two rules are intentional, stagger their schedules so they cannot overlap.
- If the resource simply takes longer to back up than the interval between runs, reduce the frequency rather than widening the window indefinitely.
- Increase the Complete within duration so a waiting job still has time once the first finishes.
What AWS documents
AWS categorises this as CONCURRENT_JOB and documents that a second job for the same resource waits, and can reach EXPIRED if the completion window runs out while waiting.
Source: AWS Backup Developer Guide — Backup job statuses
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