Performing a DR Drill

Scenarios

If the primary and DR regions and primary and DR instances are normal, you can log in to the DR instance and perform a DR drill. This section describes the precautions and how to perform a DR drill.

Precautions

• This function is supported only when streaming DR is used and the DB engine version is V2.0-3.200 or later.
• After a DR drill starts, data synchronization between the primary and DR instances is suspended. Automated backups for the DR instance are created.
• When a DR drill is being performed on the DR instance, do not remove the DR relationship from the primary instance side.

Procedure

1. Log in to the console and select the region where the DR instance is located.
2. In the navigation pane on the left, choose Disaster Recovery. Click More in the Operation column of the target DR task, and choose Enable DR Drill.

   Log Cache Space/Primary Instance Space: During the DR drill, the DR instance provides services and the incremental data is temporarily cached in the primary instance. After the drill is complete, the DR instance can perform incremental replay based on the temporarily stored incremental data. If the cached incremental data exceeds the value of this parameter, the DR instance will replay all data after the drill is complete.

3. After the DR drill is enabled, perform DR drill operations on the DR instance.
4. After the drill is complete, log in to the console and select the region where the DR instance is located. On the Disaster Recovery page, click More in the Operation column of the target DR task, and choose Disable DR Drill.
5. After the DR drill is complete, view that the DR task is restored to the status before the DR drill is performed. The data generated by the primary instance during the DR drill is synchronized to the DR instance, and the data generated by the DR instance during the DR drill is cleared.