Files
doc-exports/docs/ddm/umn/ddm_06_0017.html
wangdengke2 9a6a028567 ddm_umn
Reviewed-by: Wagner, Fabian <fabian.wagner@t-systems.com>
Co-authored-by: wangdengke2 <wangdengke2@huawei.com>
Co-committed-by: wangdengke2 <wangdengke2@huawei.com>
2025-10-10 12:17:53 +00:00

11 KiB

Restoring Metadata

DDM automatically backs up DDM instance metadata at 02:00 UTC+00:00 every day and retains the backup data for 30 days. Metadata backup is also triggered by key operations, such as deleting a schema, deleting data after shard configuration, and deleting instances.

When you delete a schema by mistake or your RDS for MySQL instances become abnormal, metadata restoration allows you to restore your DDM instance metadata and match the metadata with the RDS instance that has completed PITR to re-establish the relationship between your DDM instance and RDS instance. Metadata restoration supports only RDS for MySQL.

To restore metadata of a DDM instance, you can specify a point in time by referring to Restoring Metadata to a Point in Time, or using an available backup by referring to Restoring Metadata Using Backups.

Metadata restoration mainly restores the metadata of your DDM instance to a new DDM instance. It starts after a point-in-time recovery (PITR) for the associated data nodes is complete.

Prerequisites

  • There is a source DDM instance available and associated with an RDS for MySQL instance. This DB instance is the source data node.
  • The data from the source data node has been restored to the destination data node as it existed at a specified point in time.
  • The destination RDS for MySQL instance and the destination DDM instance must be deployed in the same VPC and subnet and have the same security group rules.

Constraints

  • The destination DDM instance is not associated with any RDS for MySQL instance and has no schemas and accounts.
  • Restoration is not supported if the destination DDM instance is in the primary network and its associated RDS for MySQL instance is in the extended network.
  • The source DDM instance must be of the version 2.3.2.11 or later, and the destination DDM instance must be of the version 3.0.8 or later.
  • Time points that data can be restored to depend on the backup policy set on original data nodes.
  • The time point to which metadata is restored must be the same as that to which an RDS for MySQL instance is restored.

Restoring Metadata to a Point in Time

  1. Log in to the DDM console.
  2. Create a new DDM instance and use it as the destination DDM instance. For details, see Creating a DDM Instance.
  3. In the DDM instance list, locate the source instance and click its name.
  4. In the navigation pane on the left, choose Backups & Restorations.
  5. Click Restore Metadata.
  6. On the displayed page, specify a time point. The source DDM instance will select an appropriate DDM metadata backup closest to the time point.

    Table 1 Parameter description

    Parameter

    Description

    Restore To

    Specify a point in time. DDM will restore metadata to this point in time using the most recent backup.

    Destination DDM Instance

    Select the DDM instance created in 2.

    Destination Data Nodes

    Select the RDS for MySQL instances that have completed PITR. DDM will match the selected data nodes with shard information in the selected metadata backup.

    For details about how to perform PITR on RDS for MySQL instances, see Restoring a DB Instance to a Point in Time.

  7. Click OK. If a message is displayed indicating that the metadata is restored successfully, the restoration is complete.

Restoring Metadata Using Backups

  1. Log in to the DDM console.
  2. Create a new DDM instance and use it as the destination DDM instance. For details, see Creating a DDM Instance.
  3. In the DDM instance list, locate the source instance and click its name.
  4. In the navigation pane on the left, choose Backups. Alternatively, go to the instance details page and choose Backups in the navigation pane on the left.
  5. Locate the required backup based on the instance name and backup time and click Restore in the Operation column.

  6. On the displayed page, configure required parameters.

    Table 2 Parameter description

    Parameter

    Description

    Backup Name

    Name of the backup to be restored.

    Destination DDM Instance

    Select the DDM instance created in 2.

    Destination Data Nodes

    Select the RDS for MySQL instances that have completed PITR. DDM will match the selected data nodes with shard information in the selected metadata backup.

    For details about how to perform PITR on RDS for MySQL instances, see Restoring a DB Instance to a Point in Time.

  7. Click OK. If a message is displayed indicating that the metadata is restored successfully, the restoration is complete.