Database Backup (DBS) runs backup tasks based on the backup policy of a backup instance. You can also manually initiate a backup task. This topic describes how to manually initiate a backup task.
Prerequisites
The data source is an ApsaraDB RDS for MySQL instance.
A backup instance is purchased and configured. For more information, see Purchase a backup instance and Configure a backup instance.
Usage notes
When you initiate a backup task, DBS checks whether a full backup task is running. If a full backup task is running, DBS does not start a new backup task. You can manually initiate a backup task only after the current backup task is complete.
When DBS backs up a database, the performance of the database is affected. We recommend that you run backup tasks during off-peak hours.
Billing
When you manually initiate a backup task, DBS charges you backup fees and storage fees of backup sets. You cannot use resource plans to offset the fees of backup instances.
Billable item | Description |
Backup fees | The free quota for data backup varies based on backup instance specifications. If the volume of backup data does not exceed the free quota for data backup, you are not charged any fees. If the volume of backup data exceeds the free quota, you are charged for the excess data. For more information, see Backup fees. |
Storage fees | The backup sets generated by a backup instance are stored in the DBS built-in storage. You are charged storage fees. For more information, see Storage fees. |
Procedure
Access the Data Source page in the DBS console. In the top navigation bar, select a region. Then, click the ID of the desired instance.
In the left-side navigation pane, click Backup Policy.
On the Backup Policy page, click the Logical Backup tab.
Click Manually Backup. DBS creates and starts a full backup task.
Optional. View the progress of the backup task.
In the left-side navigation pane, click Task Management. On the Backup Task tab, view the progress of the backup task.