AnalyticDB for MySQL can restore data to prevent data loss caused by accidental changes. When you create an AnalyticDB for MySQL cluster, the full backup and log backup features are automatically enabled to back up data of the cluster. You can view backup sets and modify data backup cycles or full backup retention periods in the AnalyticDB for MySQL console.
Usage notes
You cannot execute DDL statements on an AnalyticDB for MySQL cluster within about 10 minutes after a full backup of the cluster starts.
After you release an AnalyticDB for MySQL cluster, the backup data of the cluster is deleted. If you want to retain specific data of the cluster, you can export the data to Object Storage Service (OSS) before you release the cluster. For more information, see Export data to OSS.
View backup sets
Log on to the AnalyticDB for MySQL console. In the upper-left corner of the console, select a region. In the left-side navigation pane, click Clusters. On the Clusters page, click an edition tab. Find the cluster that you want to manage and click the cluster ID.
In the left-side navigation pane, click Backup and Restoration.
On the Backup and Restoration page, click the Data Backup tab to view information about the backup sets of the cluster, such as the backup start time, backup end time, and backup size.
NoteThe values of the Backup Size parameter that are displayed in the AnalyticDB for MySQL console vary based on the edition and the mode of the cluster.
Data Warehouse Edition in elastic mode or Data Lakehouse Edition: The values of the Backup Size parameter are the actual sizes of the backup sets in the cluster.
Data Warehouse Edition in reserved mode: The values of the Backup Size parameter are larger than the actual sizes of the backup sets in the cluster.
Modify backup settings
On the Backup and Restoration page, click the Backup Settings tab.
Click Modify Backup Settings. In the Backup Settings panel, configure the parameters that are described in the following table.
Parameter
Description
Data Backup Cycle
The days of the week on which you want to perform automatic data backups.
Backup Start Time
The start time of automatic data backups.
ImportantThe amount of time that is required to back up data varies based on the amount of data to back up. We recommend that you set the backup start time to a period of time during off-peak hours.
Full Backup Retention Period
The number of days for which you want to retain the full backup files.
If you perform full backup, snapshots of full data in a cluster are compressed and stored in other offline storage media. For metadata consistency in a distributed cluster, DDL statements are prohibited by the cluster within about 10 minutes after a full backup of the cluster starts. Full restoration from backup sets is performed by cloning clusters. Backup sets are downloaded to restore data to a new cluster. For more information, see How backup works.
NoteBy default, the full backup feature is enabled, and backup files are retained for seven days.
Backup files can be retained for 7 to 730 days.
Log Backup Retention Period
The number of days for which you want to retain the log backup files.
If you perform log backup, redo logs are uploaded in parallel by using multiple nodes in a cluster to OSS to store real-time logs. A full backup and subsequent redo logs generated within a period of time can be used to restore data at a point in time to a new cluster. For more information, see How backup works.
NoteBy default, the log backup feature is enabled, and backup files are retained for seven days. You cannot modify the retention period.
What to do next
You can clone the backup data of an AnalyticDB for MySQL cluster to a new cluster by using existing backup sets. For more information, see Clone a cluster.