Restoring a backup - AWS Backup

Restoring a backup


AWS Backup does not natively copy tags during restore jobs. For an event-driven architecture that will copy tags during restore jobs, see How to retain resource tags in AWS Backup restore jobs.

Non-destructive restores

When you use AWS Backup to restore a backup, it creates a new resource with the backup that you are restoring. This is to protect your existing resources from being destroyed by your restore activity.

How to restore

For console restore instructions and links to documentation for each AWS Backup-supported resource type, see the links at the bottom of this page.

To restore a backup programmatically, use the StartRestoreJob API operation.

The configuration values ("restore metadata") that you need to restore your resource varies depending on the resource that you want to restore. To get the configuration metadata that your backup was created with, you can call GetRecoveryPointRestoreMetadata. Restore metadata examples are also available in the links at the bottom of this page.

Restoring from cold storage typically takes 4 hours more than restoring from warm storage.

For each restore, a restore job is created with a unique job ID—for example, 1323657E-2AA4-1D94-2C48-5D7A423E7394.

Restore job statuses

You can view the status of a restore job on the Jobs page of the AWS Backup console. Restore job statuses include pending, running, completed, aborted, and failed.