Restoring a DocumentDB cluster
Use the AWS Backup console to restore Amazon DocumentDB recovery points
Restoring a Amazon DocumentDB cluster requires that you specify multiple restore options. For information about these options, see Restoring from a Cluster Snapshot in the Amazon DocumentDB Developer Guide.
To restore a Amazon DocumentDB cluster
Open the AWS Backup console at https://console.aws.amazon.com/backup
. -
In the navigation pane, choose Protected resources and the Amazon DocumentDB resource ID that you want to restore.
-
On the Resource details page, a list of recovery points for the selected resource ID is shown. To restore a resource, in the Backups pane, choose the radio button next to the recovery point ID of the resource. In the upper-right corner of the pane, choose Restore.
-
In the Configuration pane, accept the defaults or specify the options for the Cluster identifier, Engine version, Instance class, and Number of instances.
NOTE: If the default VPC does not exist when restoring, you must specify a subnet in another VPC.
-
In the Network & Security pane, "No Preferences" will be displayed.
-
In the Encryption-at-rest pane, accept the default or specify the options for the Enable encryption or Disable encryption settings.
-
In the Database options pane, type in the Port and choose the Cluster parameter group.
-
In the Log exports pane, choose the log types to publish to Amazon CloudWatch Logs. The IAM role is already defined.
-
In the Maintenance pane, specify a maintenance window or choose No preference.
-
In the Tags pane, you can choose Add tag.
-
In the Deletion protection pane, you can choose Enable deletion protection.
-
After specifying all your settings, choose Restore backup.
The Restore jobs pane appears. A message at the top of the page provides information about the restore job.
-
After your restore finishes, attach your restored Amazon DocumentDB cluster to an Amazon RDS instance.
Use the AWS Backup API, CLI, or SDK to restore Amazon DocumentDB recovery points
First, restore your cluster. Use StartRestoreJob
.
You can specify the following metadata during Amazon DocumentDB restores:
availabilityZones backtrackWindow copyTagsToSnapshot // Boolean databaseName // string dbClusterIdentifier // string dbClusterParameterGroupName // string dbSubnetGroupName // string enableCloudwatchLogsExports // string enableIAMDatabaseAuthentication // Boolean engine // string engineMode // string engineVersion // string kmsKeyId // string port // integer optionGroupName // string scalingConfiguration vpcSecurityGroupIds // string
Then, attach your restored Amazon DocumentDB cluster to an Amazon RDS instance using create-db-instance
.
-
For Linux, macOS, or Unix:
aws docdb create-db-instance --db-instance-identifier
sample-instance
/ --db-cluster-identifiersample-cluster
--engine docdb --db-instance-classdb.r5.large
-
For Windows:
aws docdb create-db-instance --db-instance-identifier
sample-instance
^ --db-cluster-identifiersample-cluster
--engine docdb --db-instance-classdb.r5.large