Data Management (DMS) provides the data tracking feature. You can use this feature to find data changes that are performed in a specific time period and generate SQL statements for rolling back the data changes. This topic describes the data tracking feature and shows you how to use this feature.
When you manage data in databases, the data may fail to meet your expectations due to accidental operations such as accidental update, delete, or write operations. In this case, you must restore the data to the normal state. A common practice is to clone databases or restore database instances, databases, or tables. To restore databases and tables, database and table backups must be prepared and managed in a fine-grained manner. This requires high costs and in-advance backup schedules.
In view of this, the data tracking feature is provided. You can use this feature to find data changes that are performed in a specific time period and generate SQL statements for rolling back the data changes as needed. After the data changes are found, a script is generated for rolling back multiple data changes at a time. Then, you can submit a data change ticket to run the rollback script to restore the data in a database.
- A database of MySQL 5.6 or later is used.
Note The MySQL database may be an ApsaraDB RDS for MySQL database, a PolarDB for MySQL database, or a self-managed database on an Elastic Compute Service (ECS) instance or in a data center. The MySQL database may also be a cloud database from other cloud service providers, or a self-managed database on a cloud server of other cloud service providers.
- The binary logging feature is enabled for the database.
- You have logged on to a database.
Note If the database instance is managed in Flexible Management or Stable Change mode, you must log on to the database instance. If the database instance is managed in Security Collaboration mode, you do not need to log on to the database instance. For more information about control modes, see Control modes.
- Go to the DMS console V5.0.
- In the top navigation bar, click Database Development. In the left-side navigation pane, choose .
- In the upper-right corner of the Data TrackingTickets page, click Data Tracking.
- On the Data Track Ticket Application page, set the parameters that are described in the following table.
Parameter Description Task Name The name of the task. This helps you find the ticket in subsequent operations and allows approvers to know the purpose of the ticket with ease. Database Name The name of a specific database in a specific database instance. You must have permissions to manage the database in DMS. Enter the prefix of a database name in the field and select the database from the matched results. Table Name The table for which you want to track data operations. Enter a keyword in the field and select a table whose name contains the keyword from the matched results. You can specify multiple tables. Track Type The type of data operation that you want to track. You can select one or more types as needed. Valid values:
DELETEstatements will be generated to roll back the INSERT operations that are tracked.
UPDATEstatements will be generated to roll back the UPDATE operations that are tracked.
INSERTstatements will be generated to roll back the DELETE operations that are tracked.
Time Range The time range in which you want to track data operations.
- If the database instance to which the database belongs is managed in Flexible Management mode, you can track data operations only in the latest 1 hour.
- If the database instance to which the database belongs is managed in Stable Change or Security Collaboration mode, you can track data operations in all time ranges. However, the time range is limited to a maximum of 48 hours in a single ticket. If the time range that you specify exceeds 48 hours, split the time range and submit multiple tickets.
Change Stakeholder The stakeholders involved in the ticket. Only users who are relevant to the ticket, including those who participate in the approval process of the ticket, can view ticket details.
- Click Submit. DMS automatically retrieves binary logs. After the binary logs are obtained, the ticket enters the Approval step.Note If the binary logging feature is disabled or you have not logged on to the database, DMS cannot obtain the binary logs.
- Wait for approval.
- After the ticket is approved, DMS downloads and parses the binary logs.
- After the binary logs are parsed, select the change records that you want to roll
back and click Export Rollback Script. Note You can also perform the following operations:
- Select multiple change records and export the rollback statements for these records at a time. By default, each page displays 10 records. A maximum of 200 records can be displayed on each page. You can specify the number of records to be displayed per page as needed.
- To view the details of a record and copy the rollback statement, click View Details to the right of the record name.
- Select one or more options from the Track Type drop-down list to filter INSERT, UPDATE, and DELETE records.
What to do next
After the rollback script is exported, you can submit a Normal Data Modify ticket. You can upload the exported script as the SQL statements for data change, run the script, and then apply changes to the database on which you want to perform changes. For more information, see Change regular data.