Restoring Data to a DB Instance

Scenarios

You can use an automated or manual backup to restore data to the point in time when the backup was created. The restoration is at the instance level.

Procedure

1. Log in to the management console.
2. Click in the upper left corner and select a region and a project.
3. Click in the upper left corner of the page, choose Databases > GaussDB(for MySQL).
4. Select the backup to be restored using either of the ways:

   In the navigation pane on the left, click Backups. On the Backups page, select the backup to be restored and click Restore in the Operation column.

   On the Instances page, click the instance name to go to the Basic Information page. On the Backups page, select the backup to be restored and click Restore in the Operation column.

5. Set Restoration Method to Create New Instance, Restore to Original, or Restore to Existing as needed.
   Figure 1 Restoring an instance from a backup
   
   1. Select Create New Instance and click OK. On the Create New Instance page, configure parameters and click Next.
      • The region, DB engine and version of the new instance are the same as those of the original instance and cannot be changed.
      • The default database port is 3306.
      • Other settings are the same as those of the original instance by default and can be modified. For details, see Buying a DB Instance.
   2. Select Restore to Original and click Next. In the displayed dialog box, click OK.
      • Data on the original instance will be overwritten and the original DB instance will be unavailable during the restoration.
      Figure 2 Restoring to the original DB instance
      
   3. Select Restore to Existing, select the target DB instance, and click Next.
      • Restoring data to an existing DB instance will overwrite data and password of user root on it and cause the existing DB instance to be unavailable during the restoration. DB instances will not be displayed unless they have the same DB engine type, version, and table name case sensitivity as the original DB instance.
      • If the original password of the existing DB instance cannot be used to connect to the database, you can reset the password.
      Figure 3 Restoring to an existing instance
      

6. View the restoration results.
   • Create New Instance: After the creation is complete, the instance status changes from Creating to Available. The new instance is independent from the original one and includes the data before the backup was created. If you want to offload read pressure from the primary node, create one or more read replicas for the new instance.

     A full backup is triggered after the new instance is created.

   • Restore to Original and Restore to Existing: When the instance status changes from Restoring to Available, the restoration is complete.

APIs

• Restoring Data to the Original Instance or an Existing Instance
• Querying the Restoration Time Range