Help Center/ Distributed Cache Service/ User Guide/ Backing Up or Restoring Instance Data/ Restoring DCS Instances
Updated on 2024-12-16 GMT+08:00
View PDF
Share

Restoring DCS Instances

This section describes how to restore instances on the DCS console. This function helps restore instances deleted by mistake.

To migrate backup data to other DCS instances, see Backup Import Between DCS Redis 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)

Prerequisites

  • A master/standby, cluster, or read/write splitting DCS instance 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 management console and select the region where your instance is located.
  3. In the navigation pane, choose Cache Manager.

    Filter DCS instances to find the desired DCS instance. 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.
  7. Click OK to start instance restoration.

    Information in the Description text box cannot exceed 128 bytes.

    You can view the results of all restoration tasks on the Restoration History page. The records cannot be deleted.
    • Instance restoration takes 1 to 30 minutes.
    • While being restored, DCS instances do not accept data operation requests from clients because existing data is being overwritten by the backup data.