As your business grows, the amount of data in your online databases increases. As a result, table queries slow down, and your business operations are affected. To resolve this problem, Data Management (DMS) provides the data archiving feature. You can use this feature to archive the data of large tables to Object Storage Service (OSS) buckets or ApsaraDB for Lindorm instances. You can also use this feature to delete archived data from large tables and recycle the storage space that is occupied by large tables. This way, you can improve query performance and reduce the costs of online storage. This topic describes how to archive the data of large tables to OSS buckets that are connected to Database Backup (DBS).
Prerequisites
- A MySQL database, such as an ApsaraDB RDS for MySQL database or a PolarDB for MySQL database, is used.
- DBS is activated. For more information, see How do I activate DBS?.
- Data Lake Analytics (DLA) is activated. For information about how to activate DLA, see Activate DLA.
- You are a DMS administrator, database administrator (DBA), or regular user.
Note A regular user must have the export permissions on the database. For more information about how to apply for the permissions, see Manage permissions.
Billing
Procedure
Cyclic scheduling
Configuration item | Description |
---|---|
Scheduling Cycle | Select the cycle based on which DMS executes the data archiving task.
|
Timed Scheduling | Specify one of the following scheduling methods:
|
Specified Time |
|
Specific Point in Time | Specify the point in time at which DMS executes the data archiving task.
For example, if you select 02:55, DMS executes the data archiving task at 02:55 on the days that you select. |
Cron Expression | You do not need to configure this parameter. DMS automatically generates a cron expression based on the values that you specify for the preceding parameters. |