Disaster Recovery Center

更新时间:
复制 MD 格式

On the Disaster Recovery Center page in Data Backup, you can view the number of database instances, their running status, and cross-region backup status. You can also enable or disable the cross-region backup feature.

Supported database instances

Procedure

Disaster Recovery Center page

  1. Log on to Data Management (DMS) 5.0.

  2. In the top navigation bar, choose Security and Compliance (DBS) > Data Backup (DBS) > Disaster Recovery Center.

    Note
    • If you are using the console in simple mode, click the 2023-01-28_15-57-17.png icon in the upper-left corner and choose All Functions > Security and Compliance (DBS) > Data Backup (DBS) > Disaster Recovery Center.

    • You can also go directly to the Disaster Recovery Center page.

    The following table describes the main parameters on this page.

    Parameter

    Description

    Cloud database instances

    The total number of database instances.

    Instances with cross-region backup disabled

    The number of database instances for which cross-region backup is disabled.

    Instances with cross-region backup enabled

    The number of database instances for which cross-region backup is enabled.

    Cross-region backup

    All database instances.

    Instances with cross-region backup disabled

    The database instances for which cross-region backup is disabled.

Filter instances

  1. Go to the Disaster Recovery Center page.

  2. Click the Cross-region backup or Cross-region backup disabled tab.

  3. Filter the instances.

    You can enter an instance ID in the search box, or filter the list by Region or Database Type.

    Note

    Region is a required parameter, and Database type defaults to all types.

Enable cross-region backup

  1. Go to the Disaster Recovery Center page.

  2. Click the Cross-region backup or Cross-region backup disabled tab.

  3. Find the target instance and click Settings in the Actions column.

    Note
    • You can use the filter feature to find the target instance.

    • For instances that do not support the cross-region backup feature, the Settings button in the Actions column is unavailable (grayed out).

  4. In the Cross-region Backup Settings dialog box, configure the parameters.

    Set Cross-region Backup Status to Enabled and configure the other parameters. For more information, see RDS MySQL cross-region backup, RDS SQL Server cross-region backup, RDS PostgreSQL cross-region backup, or PolarDB for MySQL cross-region backup.

  5. Read and select the checkboxes for the billing description and the Data Cross-border Compliance Commitment.

  6. Click OK.

    Note
    • The page automatically refreshes.

    • After the feature is enabled, the Cross-region Backup Status for the instance changes to Enabled.

Disable cross-region backup

  1. Go to the Disaster Recovery Center page.

  2. Optional: Click the Cross-region backup tab.

  3. Find the target instance and click Settings in the Actions column.

    Note
    • You can use the filter feature to find the target instance.

    • For instances that do not support the cross-region backup feature, the Settings button in the Actions column is unavailable (grayed out).

  4. In the Cross-region Backup Settings dialog box, set Cross-region Backup Status to Disabled.

  5. Read and select the checkboxes for the billing description and the Data Cross-border Compliance Commitment.

  6. Click OK.

    Note
    • The page automatically refreshes.

    • After the feature is disabled, the Cross-region Backup Status for the instance changes to Disabled.

FAQ

  • Q: Does the Disaster Recovery Center support self-managed databases?

    A: No, it does not.

  • Q: How can I manually refresh the resource overview or the instance list?

    A: In the upper-right corner of the Resource Overview area or the instance list, click the image icon. This refreshes both the overview and the list.

  • Q: Why are there no instances on the Cross-region backup and Cross-region backup disabled tabs in the Disaster Recovery Center?

    A: This can occur if your filter criteria are incorrect or you lack sufficient access permissions.