This topic describes how to switch an ApsaraDB RDS for MySQL instance from the disaster recovery role to the primary role. The disaster recovery RDS instance resides in a different region than the primary RDS instance. If both the primary and secondary RDS instances are unavailable due to natural disasters, you can switch the disaster recovery RDS instance to the primary role. Then, you must immediately update the endpoint configuration on your application. This minimizes the downtime of your database system.

Prerequisites

A disaster recovery RDS instance is created. For more information, see Create a disaster recovery ApsaraDB RDS for MySQL instance.

Precautions

After the disaster recovery RDS instance is switched to the primary role, you cannot switch the instance back to the disaster recovery role.

Procedure

  1. Log on to the ApsaraDB RDS console.
  2. In the left-side navigation pane, click Instances. In the top navigation bar, select the region where the disaster recovery RDS instance resides.
    Note The primary and disaster recovery RDS instances reside in different regions. You must select the region where the disaster recovery RDS instance resides.
  3. Find the disaster recovery RDS instance and click its ID.
  4. Click Switch to Primary Instance. In the message that appears, click OK.
    Switchover to the primary role
    Note After the switchover is complete, you must update the endpoint configuration on your application. This update requires you to replace the endpoint of the original primary RDS instance with the endpoint of the new primary RDS instance.