Restoring Data to a New or Existing Instance

Scenarios

GeminiDB Mongo API allows you to use an existing backup to restore data to a new or existing instance.

Precautions

This function is in the open beta test (OBT) phase. To use this function, contact customer service.

Procedure

1. Log in to the management console.
2. In the service list, choose Databases > GeminiDB Mongo API.
3. Restore a DB instance from the backup.

   Method 1

   1. On the Instances page, locate the instance whose backup you want to restore and click its name.
   2. On the Backups & Restorations page, locate the target backup and click Restore.
   Figure 1 Backups and restorations
   

   Method 2

   On the Backups page, locate the backup that you want to restore and click Restore in the Operation column.

   Figure 2 Backup management
   

4. In the displayed dialog box, confirm the instance details and restoration method and click OK.
   • Create New Instance
     Figure 3 Restoring data to a new instance
     

     The Create New Instance page is displayed. Configure the new DB instance details based on your service requirements.

     • The default API type and DB engine version are the same as those of the original instance and cannot be changed.
     • GeminiDB automatically calculates the minimum storage space required for restoration based on the size of the selected backup file. The storage capacity depends on the instance specifications, and must be an integer.
     • You need to set a new administrator password.
     • To modify other parameters, see the description of buying DB instances of other DB engines in the Getting Started with GeminiDB Mongo.
   • Restore to Existing
     Select an existing instance and click OK.

     

     • You can restore a deleted instance to an existing instance from a backup if available.
     • Restoring to an existing DB instance will overwrite the data, and the existing DB instance becomes unavailable during the restoration.
     • After data is restored to an existing DB instance, the username and password saved in the backup file will overwrite those of the existing DB instance.
     • Only DB instances that have the same number of nodes, use the same or later DB API version, and have the same or higher specifications than the original DB instance can be selected.
     • The storage space of the instance that you want to restore the backup to must be greater than or equal to the size of the backup. Otherwise, the restoration task fails.

     Figure 4 Restore DB Instance
     

5. View the restoration results.
   • Create New Instance

     A new instance is created using the backup data. The restoration is successful if the status of the new instance changes from Creating to Available.

     After the restoration is complete, a full backup will be automatically triggered.

     The new DB instance is independent from the original one.

   • Restore to Existing

     On the Instances page, the status of the instance changes from Restoring to Available.

     If automated backup is enabled, a full backup will be triggered after the restoration is complete. Otherwise, the full backup will not be triggered.