Data Management:Archive data to an OSS bucket

Usage notes

• If the source table has a composite primary key that consists of three columns or the source table has three or more unique keys, the data archiving task may fail. We recommend that you fully test the source tables that have a three-column composite primary key before you perform data archiving, or use other archiving methods such as Database Backup (DBS).

• The data archiving feature is supported only in the Singapore and Indonesia (Jakarta) regions.

Procedure

1. Log on to the DMS console V5.0.
2. In the top navigation bar, choose Solution > Data archiving.

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

4. On the Ticket Application page, configure parameters to create a data archiving ticket. The following table describes the parameters.

   Parameter	Description
   Task Name	The name of the data archiving task. We recommend that you specify a descriptive name that makes it easy to identify the task.
   Archiving Destination	The destination to which you want to archive data. Select OSS.
   OSS Instance	The destination OSS instance to which you want to archive data. Note Select a Standard or an IA OSS instance.
   OSS BUCKET	The OSS bucket that belongs to the selected OSS instance. Important If you cannot find an OSS bucket that you require in the selected OSS instance, log on to the OSS instance in the DMS console. For more information, see Register an OSS bucket. The archived data is stored in the archive folder in the OSS bucket. Do not delete the folder.
   Source Database	The source database from which you want to archive data.
   Archive Configuration	Specifies one or more tables whose data you want to archive. Optional. Specify one or more filter conditions for querying data to be archived in the specified tables. Note If you want to use time variables in scenarios such as archiving data generated six months ago, you can set the variables in the Variable Configuration section before you configure the parameters in the Archiving Configuration section. Optional. Click Add to add more source tables.
   Archive Table Mapping	The table settings to be used in the destination bucket. You can find a table and click Edit in the Actions column to configure the table information.
   Variable Configuration	Optional. The variables that are used when you configure conditions for filtering archived data. For example, you have created a time variable named 6_month_ago in the yyyy-MM-dd format and set the offset to - 6 Month. In this case, if the current date is August 12, 2021, the value of the ${6_month_ago} variable is 2021-02-11, which indicates February 11, 2021. For more information about how to configure time variables, see the Configure time variables section of the "Variables" topic.
   Post-behavior	Specifies whether to delete the archived data from the source tables. If you clear Clean up the archived data of the original table (delete-No Lock), the archived data is not deleted from the source tables. If you select Clean up the archived data of the original table (delete-No Lock), DMS automatically deletes the archived data from the source tables. The source tables are not locked during the deletion process. Specifies whether to verify archived data. If you clear Verify the archived data (time-consuming), DMS does not verify the archived data. If you select Verify the archived data (time-consuming), DMS compares the archived data with the original data in the source database and displays data discrepancies in addition to the archived data. The amount of time consumed for archived data verification depends on the amount of archived data.
   Operation Mode	The method to be used for running the data archiving task. Valid values: Single execution: After the data archiving ticket is approved, DMS runs the data archiving task only once. Cyclic scheduling: After the data archiving ticket is approved, DMS runs the data archiving task based on the schedule that you specify. For more information, see the Periodic scheduling section of the "Archive data to a Lindorm instance" topic.

5. Click Submit.

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

   Note

   The data archiving feature implements data archiving and post-behavior based on the UTC+0 time zone regardless of the time zone of the database to be archived.

6. Optional. After the data is archived and you verify that the archived data is correct, delete the archived data from the source tables and optimize the storage usage of the source tables.

   1. Delete the archived data from the source tables.

      • If you select Clean up the archived data of the original table (delete-No Lock) for the Post-behavior parameter, DMS deletes the archived data from the source tables and generates temporary backup tables in the source database.

        To delete the temporary backup tables from the source database, create a Normal Data Modify ticket. For more information, see Normal data modify.

        Note

        In the lower part of the Data Archiving Ticket Details panel, click Click here to view the DROP statement used to drop the temporary table. and copy the SQL statements that are used to delete the temporary backup tables.

      • If you clear Clean up the archived data of the original table (delete-No Lock) for the Post-behavior parameter, you need to manually delete the archived data from the source tables.

        To delete the archived data from the source tables, create a Normal Data Modify ticket.

   2. To optimize the storage usage of the source tables, create a lock-free change ticket. For more information, see Perform lock-free DDL operations.

      Note

      In the lower part of the Data Archiving Ticket Details panel, click View SQL Statements Used to Optimize Storage Usage of Source Table and copy the SQL statements that are used to optimize the storage usage of the source tables.

7. Query the archived data. For more information, see the Query data archived to OSS buckets section of the "Query data archived to OSS buckets or dedicated storage" topic.

Restore the archived data to the source database