Scenarios

This section describes how to restore a cluster instance from a backup.

Restoration Precautions

• Currently, DDS cluster instances of Community Edition can be restored to a new DB instance or the original DB instance.
• When you restore the DB instance from a backup file, a full backup file is downloaded from OBS and then restored to the DB instance at an average speed of 40 MB/s.

Method 1

1. Log in to the DDS console.
2. On the Instance Management page, click the target cluster instance.
3. In the navigation pane on the left, click Backups & Restorations.
4. On the Backups & Restorations page, locate the target backup and click Restore in the Operation column.
5. Select either of the following restoration methods and click OK.
   • Create New Instance

     The Create New Instance page is displayed for you to create a DB instance using the backup data. The new DB instance is independent from the original one.

     • You are recommended to deploy the restored DB instance in a different AZ to ensure that applications will not be adversely affected by the failure in any single AZ.
     • The database type, DB instance type, compatible MongoDB version, storage engine, storage type, and shard quantity must be the same as those of the original and cannot be changed.
     • The number of mongos nodes is 2 by default and ranges from 2 to 32. You can specify the quantity.
     • The storage space is the same as that of the original instance by default. You can only increase the storage space.
     • Other settings are the same as those of the original DB instance by default and can be modified. For details, see Buying a Cluster Instance (Community Edition).
   • Restore to Original
     

     • Restoring to the original DB instance will overwrite all existing data and the DB instance will be temporarily unavailable during the restoration.
     • The administrator password of the database instance remains unchanged after the restoration.

     Check that the status of the DB instance on the Instance Management page is Restoring.

Method 2

1. Log in to the DDS console.
2. In the navigation pane on the left, click Backup Management.
3. On the Backup Management page, locate the target backup on the Clusters tab and click Restore in the Operation column.
   • If you use an automated backup, go to 4.
   • If you use a manual backup, check whether the original instance of the manual backup exists:
     • If yes, go to 4.
     • If no, you can only restore the backup to a new DB instance. Go to Create New Instance.

4. Select either of the following restoration methods and click OK.
   • Create New Instance

     The Create New Instance page is displayed for you to create a DB instance using the backup data. The new DB instance is independent from the original one.

     • You are recommended to deploy the restored DB instance in a different AZ to ensure that applications will not be adversely affected by the failure in any single AZ.
     • The database type, DB instance type, compatible MongoDB version, storage engine, storage type, and shard quantity must be the same as those of the original and cannot be changed.
     • The number of mongos nodes is 2 by default and ranges from 2 to 32. You can specify the quantity.
     • The storage space is the same as that of the original instance by default. You can only increase the storage space.
     • Other settings are the same as those of the original DB instance by default and can be modified. For details, see Buying a Cluster Instance (Community Edition).
   • Restore to Original
     

     • Restoring to the original DB instance will overwrite all existing data and the DB instance will be temporarily unavailable during the restoration.
     • The administrator password of the database instance remains unchanged after the restoration.

     Check that the status of the DB instance on the Instance Management page is Restoring.