Home / AWS Backup errors

AWS Backup errors, explained

Every AWS Backup failure we have catalogued — what the message actually means, why it happens, and the specific setting to change. Built from the AWS Backup Developer Guide and from failures seen in production.

Backup job EXPIRED — did not finish inside the window
AWS Backup gives every job a start window and a “Complete within” window.
Warning EXPIRED
Job stuck in CREATED then EXPIRED — start window too short
During the start window a job stays in CREATED until it begins.
Warning CREATED
AccessDenied / insufficient privileges
AWS Backup assumes an IAM role to perform the backup.
Critical FAILED
KMS key not accessible / cannot decrypt
The backup role cannot use the KMS key that encrypts the source (common with encrypted RDS/EBS).
Critical FAILED
Lifecycle outside the valid range for the vault
The vault has a vault lock setting MinRetentionDays or MaxRetentionDays, and the retention in your backup rule falls outside that range.
Warning FAILED
Windows VSS backup failed (EC2)
Application-consistent Windows backups rely on VSS and the SSM Agent.
Warning FAILED
RDS / Aurora backup expired before completion
Starting a backup from the Amazon RDS console can collide with an Aurora cluster's own backup job.
Warning EXPIRED
VMware — unsupported disk size / independent disk
Two distinct causes share this message. AWS Backup does not support VMs with disks in independent persistent or independent non-persistent mode.
Warning FAILED
Copy job failed — retention or cross-account mismatch
A copy job fails when the retention requested is outside the destination vault’s allowed range, or when a cross-account copy is attempted between accounts that are not in the same…
Warning FAILED
Throttling / too many concurrent backups
Firing a very large number of jobs in the same minute can hit AWS API rate limits.
Information FAILED
Database backup fails near the maintenance or automatic backup window
AWS database services cannot start a backup during, or in the hour before, their maintenance window or their automatic backup window.
Critical FAILED
On-demand backups work but scheduled ones fail with a KMS error
The exact message is “The source snapshot KMS key does not exist, is not enabled or you do not have permissions to access it.” The confusing part is that on-demand backups still…
Critical FAILED
EFS backup never runs — only one concurrent backup allowed
An EFS file system allows only one backup at a time.
Warning EXPIRED
Backup fails when the source resource carries tags
If your source resources have tags, or you want tags copied onto recovery points, the AWS Backup IAM role needs backup:TagResource on recovery points.
Critical FAILED
Tag-based selections silently back up nothing
If the role has tag:GetResources but a Service Control Policy blocks it, AWS Backup cannot resolve a tag-based resource selection.
Critical FAILED
DynamoDB backup fails while the table is being created
A DynamoDB table cannot be backed up while it is still being created, which typically takes a couple of minutes.
Information FAILED
EBS backups fail after hitting the per-Region quota
EBS has a soft quota of 100,000 backups per Region per account.
Warning FAILED
VMware — no gateways available to work on job
Every backup gateway processes a maximum of four concurrent backup or restore jobs.
Critical FAILED
VMware — abort signal detected
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…
Critical ABORTED
VMware — failed to process backup data / error opening disk
AWS Backup could not open one or more of the VM's virtual disks.
Critical FAILED
VMware — Change Block Tracking invalid or unavailable
The backup still completed — AWS fell back to its own change-detection mechanism.
Information COMPLETED
VMware — failed to create snapshot during snapshot creation
AWS Backup could not get VMware to take a snapshot of the VM.
Critical FAILED
Another backup is already running for this resource
AWS Backup will not run two backup jobs against the same resource at once.
Warning FAILED
Internal error during a cloud operation
AWS Backup reported an internal error while starting the operation.
Warning FAILED
VMware — upload failed or timed out during data ingestion
The link between the VM environment and AWS is congested or too slow to carry the backup within its window.
Critical FAILED

Or let something else read them for you

BackupLens matches every failed job against this catalogue automatically and sends you the cause and the fix by email or Telegram. Read-only AWS access, no agents, nothing installed in your account.

Start free trial