Archive data to Lindorm

Usage notes

Billing

The fee for purchasing the destination instance.

Archive data

1. Log in to DMS 5.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 of the page, click Data Archiving.

4. On the New Data Archive Ticket page, configure the ticket information.

   Parameter	Required	Description
   Task Name	Yes	Enter a clear and specific task name to reduce communication costs.
   Archive Destination	Yes	Select Lindorm.
   Lindorm Instance	Yes	Search for and select the destination ApsaraDB for Lindorm instance.
   Source Database	Yes	Search for and select the source database.
   Archive Configuration	Yes	Select the table to archive. Optional: Enter the filter conditions for the data to be archived. Example: gmt_modified<='${6_month_ago}'. Note If you need to use a time variable, for example, to archive data from six months ago, first configure the variable in the variable configuration section. Optional: Click Add to add multiple source tables.
   Archive Table Mapping	No	You can click Edit in the Actions column of the table name to edit the table name, column information, sharding key, and partition key after the source table is archived to the destination database.
   Variable Configuration	No	Define time variables for filter conditions. For example, create a variable named 6_month_ago with format yyyy-MM-dd and offset -6 Month. If today is August 12, 2021, ${6_month_ago} resolves to 2021-02-11. For more information, see the "Configure time variables" section of the Variables topic.
   Post-action	No	If you select Clean up archived data in the source table (delete-lock-free), after archiving is completed, the system automatically deletes the archived data in the source table by using a lock-free data change DELETE statement. However, deleting the source table generates a temporary backup table in the source database to store the archived data. Ensure that the source database has enough space to avoid instance unavailability caused by insufficient space. Clean up the temporary backup table: After you confirm that data archiving is complete and the data is correct, you can create a Standard data change ticket to clean up the temporary backup table in the source database. If you do not select Clean up archived data in the source table (delete-lock-free), you need to manually delete data in the source table and optimize space after data archiving is complete. Clean up data in the source table: Create a normal data change ticket to clean up the archived data in the database. For information about how to create a normal data change ticket, see Standard data change. Optimize space in the source table: Create a lock-free change ticket to optimize the space of the source table. For information about how to create a lock-free change ticket, see Perform lockless schema changes using lockless change tickets. If you select Verify archived data, the archived data is verified when the archive task is run. The verification includes the archive table name, source database, and the number of SQL statements. You can view the details by clicking Verification Details.
   Run Mode	Yes	Select a run mode. The following modes are supported: Run Once: After the ticket is approved, the archive task runs only once. Periodic scheduling: After the ticket is approved, the archive task runs based on the deployed periodic schedule. For more information, see Periodic scheduling.

5. Click Submit.

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

7. Query the data after archiving is successful.

Query archived data

Periodic scheduling