Restoring DCS Instances

Notes and Constraints

• You can enable or disable multi-DB for a Proxy Cluster instance. Data backed up when multi-DB is enabled cannot be restored to the instance after multi-DB is disabled.
• This function becomes unavailable after the following changes.
  • Instance scale-in
  • Cluster instance scale-out
  • Instance type changes (from master/standby to read/write splitting not included)
• During restoration, the instance is unable to process data requests from a client for a while.

Prerequisites

• A master/standby, cluster, or read/write splitting DCS instance is available, and is in the Running state.
• A backup task has been run to back up data in the instance to be restored and the backup task succeeded.

Procedure

1. Log in to the DCS console.
2. Click in the upper left corner of the console and select the region where your instance is located.
3. In the navigation pane, choose Cache Manager.

   DCS instances can be filtered on the Cache Manager page. Currently, you can search instances by name, specification, ID, IP address, AZ, status, instance type, cache engine, and many other attributes.

4. Click the name of the desired DCS instance to go to the instance details page.
5. On the instance details page, click Backups & Restorations.

   A list of historical backup tasks is then displayed.

6. Click Restore in the row containing the chosen backup task.

   A description can be entered within 128 characters.

7. Click OK to start instance restoration.
   • The restoration result can be queried on the Restoration History tab page. The data is restored when the restoration task is in the Successful state.
   • The restoration history is valid for 7 days, and cannot be manually deleted.
   • Instance restoration takes 1 to 30 minutes.
   • Restoration automatically deletes the original instance data and replaces it with the backup.

Related Document

To restore an instance by calling an API, see Restoring a DCS Instance.