vpruthi/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity
doc-exports/docs/dds/umn/dds_03_0043.html
Wang , Deng Ke 519944c837 DDS UMN 20221101 version 
Reviewed-by: Hasko, Vladimir <vladimir.hasko@t-systems.com>
Co-authored-by: Wang , Deng Ke <wangdengke2@huawei.com>
Co-committed-by: Wang , Deng Ke <wangdengke2@huawei.com>
2022-11-24 09:05:29 +00:00

5.1 KiB
Raw Permalink Blame History

Restoring a Replica Set Instance from a Backup

Scenarios

This section guides you on how to restore a replica set instance from a backup.

Currently, DDS only supports restoring backups to a new DB instance.

Method 1

  1. Log in to the DDS console.
  2. On the Instance Management page, click the target replica set instance.
  3. In the navigation pane on the left, click Backups & Restorations.
  4. On the Backups & Restorations page, locate the target backup in the backup list and click Restore in the Operation column. In the displayed dialog box, click OK.
  5. On the displayed page, create a DB instance using the same configurations as the backup. 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, improving data reliability.
    • The database type, DB instance type, compatible MongoDB version, storage engine, and storage type must be the same as those of the original and cannot be changed.
    • 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 section Creating a Replica Set Instance.

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, click the Replica Sets tab, locate the backup to restore, and click Restore in the Operation column. In the displayed dialog box, click OK.
  4. On the displayed page, create a DB instance using the same configurations as the backup. 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, improving data reliability.
    • The database type, DB instance type, compatible MongoDB version, storage engine, and storage type must be the same as those of the original and cannot be changed.
    • 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 section Creating a Replica Set Instance.

Parent topic: Backup and Restore