ApsaraDB RDS:Use data tracking of DMS to restore data

Choose a restoration method

Use the following table to decide which restoration method fits your situation before proceeding.

Use data tracking when you need to roll back specific rows from a known time window and want to avoid the overhead of restoring an entire instance.

Prerequisites

Before you begin, ensure that you have:

• A MySQL 5.6 or later database

• Binary logging enabled for the database

• Logged on to the database in DMS (required for Flexible Management and Stable Change modes; not required for Security Collaboration mode)

Limitations

• Only DML operations (INSERT, UPDATE, DELETE) can be tracked. DDL operations cannot be tracked.

• Flexible Management mode: tracking is limited to the previous 30 minutes, and rollback or rebuild scripts cannot be exported.

• Stable Change or Security Collaboration mode: tracking is limited to the binary log retention period.

• A single data tracking ticket covers a maximum of 48 hours. For longer time ranges, split the range across multiple tickets.

• If binary logging is disabled or you have not logged on to the database, DMS cannot retrieve binary logs.

Track data changes and generate a rollback script

1. Log on to the DMS console V5.0.

2. In the top navigation bar, click Database Development > Data Tracking > Data Tracking Ticket.

   If you use the DMS console in simple mode, move the pointer over the icon in the upper-left corner and choose All Features > Database Development > Data Tracking > Data Tracking Ticket.

3. In the upper-right corner of the Data Tracking Ticket page, click Data Tracking.

4. On the Data Tracking Tickets page, configure the following parameters and click Submit. After you click Submit, DMS automatically retrieves the binary logs. The ticket moves to the Approval step.

   Parameter	Description
   Task Name	Enter a name that helps you and approvers identify the purpose of the ticket.
   Database Name	Select the database whose data you want to track. You must have management permissions for the database in DMS. Type a prefix to filter the list.
   Table Name	Select one or more tables to track.
   Track Type	Select the operation types to roll back: Insert (generates INSERT rollback statements), Update (generates UPDATE rollback statements), or Delete (generates DELETE rollback statements).
   Time Range	Specify the time window covering the accidental change. Flexible Management mode: limited to the previous 30 minutes. Stable Change or Security Collaboration mode: any range within the binary log retention period, up to 48 hours per ticket.
   Change Stakeholder	Select the stakeholders who need access to ticket details. Only the selected stakeholders and ticket approvers can view the ticket.

5. Wait for the ticket to be approved.

   By default, the database administrator (DBA) of the selected database approves data tracking tickets. For details about approval rules, see Data tracking.

6. After approval, wait for DMS to download and parse the binary logs.

7. After parsing completes, filter the results by Track Type, Table Name, or Column Name to isolate the rows you want to roll back. Select the target records and click Export Rollback Script. The rollback script is downloaded to your computer.

   To review an individual record before exporting, click View Details to see the full row data and copy the rollback statement.

Apply the rollback script

After exporting the rollback script, choose how to apply it based on the number of affected rows:

• Few affected rows: Run the rollback statements directly in the SQL Console.

• Many affected rows: Submit a normal data change ticket and upload the exported rollback script as an attachment. DMS applies the SQL statements to the selected database.

API reference

To automate data tracking with the DMS API, use the following operations:

• CreateDataTrackOrder

• GetDataTrackJobDegree

• GetDataTrackJobTableMeta

• GetDataTrackOrderDetail

• SearchDataTrackResult

• DownloadDataTrackResult

• QueryDataTrackResultDownloadStatus