Archive data to Lindorm

Notes

Billing

You are charged for the destination instance that you purchase.

Archive data

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

2. In the top navigation bar, choose Solution > Data Archiving.

   Note

   If you use the DMS console in simple mode, move the pointer over the icon in the upper-left corner of the DMS console and choose All Features > Solution > Data Archiving.

3. In the upper-right corner, click Data Archiving.

4. On the Create Data Archiving Ticket page, configure the parameters.

   Configuration Item	Required	Description
   Task Name	Yes	Enter a clear and descriptive task name to improve communication efficiency.
   Archive Destination	Yes	Select Lindorm.
   Lindorm Instance	Yes	Search for and select the destination Lindorm instance.
   Source Database	Yes	Search for and select the source database.
   Archive Configuration	Yes	Select the tables whose data you want to archive. Optional: Enter a filter condition for the data to be archived. Example: gmt_modified<='${6_month_ago}'. Note To use a time variable, for example, to archive data from six months ago, configure the variable in the Variable Configuration section first. Optional: Click Add to add multiple source tables.
   Archived Table Mapping	No	In the Actions column, you can click Edit next to a table name to edit the table name, column information, sharding key, and partition key for the archived table in the destination database.
   Variable Configuration	No	You can use the configured variables when you set filter conditions. For example, set the time variable to 6_month_ago, the time format to yyyy-MM-dd, and the offset to -6 months. If the current date is 2021-08-12, the value of the ${6_month_ago} variable is 2021-02-11. For more information about how to configure time variables, see Configure time variables.
   Post Actions	No	If you select Clean up archived data from the source table (delete-lockless), the system automatically deletes the archived data from the source table after the archive task is complete. The deletion is performed using a lockless DELETE statement. However, a temporary backup table that stores the archived data is created in the source database. Make sure that the source database has sufficient space to prevent the instance from becoming unavailable. Clean up the temporary backup table: After you confirm that the data is archived correctly, you can create a regular data change ticket to clean up the temporary backup table in the source database. If you do not select Clean up archived data from the source table (delete-lockless), you must manually delete the data from the source table and optimize the table space after the data is successfully archived. Delete data from the source table: Create a regular data change ticket to delete the archived data from the database. For more information about how to create a regular data change ticket, see Regular data change. Optimize the source table space: Create a lockless change ticket to optimize the source table space. For more information about how to create a lockless change ticket, see Use a lockless change ticket to perform lockless schema evolution. If you select Validate archived data, the system validates the archived data when the archive task runs. The validation includes the archived table name, source database, and the number of SQL statements. You can click Validation Details to view the details.
   Run Mode	Yes	Select a run mode. The following modes are supported: One-time Execution: After the ticket is approved, the archive task runs only once. Recurring Schedule: After the ticket is approved, the archive task runs based on the configured recurring schedule. For more information about the configuration, see Recurring schedule.

5. Click Submit.

6. After the data archiving ticket is approved, DMS automatically runs the data archiving task.

   If the data archiving task fails to be executed, you can click Details in the Execute step to view the logs of the data archiving task and identify the cause of the task failure. If an issue occurs due to a network or database connection failure, you can click Retry Breakpoint to restart the task.

7. Query the data after it is successfully archived.

Query data after archiving

Recurring schedule