AWS Backup
Developer Guide

The AWS Documentation website is getting a new look!
Try it now and let us know what you think. Switch to the new look >>

You can return to the original look by selecting English in the language selector above.

Troubleshooting AWS Backup

When you use AWS Backup, you might encounter issues when working with backup plans, resources, and backup vaults. The following sections can help you troubleshoot some common issues that might occur.

For general questions about AWS Backup, see the AWS Backup FAQ. You can also search for answers and post questions in the AWS Backup forum.

Troubleshooting General Issues

When you back up and restore resources, you not only need permission to use AWS Backup, you must also have permission to access the resources that you want to protect. For more information about access control using AWS Identity and Access Management (IAM) with AWS Backup, see Access Control.

If you run into issues with backing up and restoring a particular resource type, it can be helpful to review the troubleshooting topic for that resource. For more information about troubleshooting other AWS services, see the following:

If AWS Backup fails to create or delete a resource, you can learn more about the issue by using AWS CloudTrail to view error messages or logs. For more information about using CloudTrail with AWS Backup, see Logging AWS Backup API Calls with AWS CloudTrail.

Troubleshooting Creating Resources

The following information can help you troubleshoot problems with creating backups.

  • Creating backups for DynamoDB tables will fail while tables are being created. Creating a DynamoDB table typically takes a couple of minutes.

  • Backing up Amazon EFS file systems can take up to 7 days when the file systems are very large. Only one concurrent backup at a time can be queued for an Amazon EFS file system. If a subsequent backup is queued while a previous one is still in progress, the backup window can expire and no backup is created.

  • Amazon EBS has a soft limit of 100,000 backups per AWS Region per account, and additional backups fail when this limit is reached. If you reach this limit, you can delete excess backups or request a limit increase. For more information about requesting a limit increase, see AWS Service Limits.

  • When creating Amazon RDS backups, consider the following:

    • Amazon RDS has a soft limit of 100 backups per AWS Region per account, and additional backups will fail when this limit is reached. If you reach this limit, you can delete excess backups or request a limit increase. For more information about requesting a limit increase, see AWS Service Limits.

    • If you initiate a backup either through a backup plan or by creating an on-demand backup, it will fail if it is scheduled during the daily user-configurable 30-minute backup window. For more information about automated Amazon RDS backups, see Working With Backups in the Amazon RDS User Guide.

    • Consecutive backups for Amazon RDS must be scheduled at least 6 hours apart.

    • Backups that are initiated during a maintenance window will fail. For more information about Amazon RDS maintenance windows, see Maintaining a DB Instance in the Amazon RDS User Guide.

Troubleshooting Deleting Resources

Recovery points that are created by AWS Backup cannot be deleted in the console window of the protected resource. You can delete them on the AWS Backup console by selecting them in the vault where they are stored and then choosing Delete.

To delete a recovery point or a backup vault, you need the appropriate permissions. For more information about access control using IAM with AWS Backup, see Access Control.