Database Backup:Modify the backup time and advanced settings

Procedure

1. Log on to the DBS console. In the left-side navigation pane, click Backup Schedules.

2. On the Backup Schedules page, find the backup schedule that you want to manage and click Manage in the Actions column. The Configure Task page appears.

3. In the Basic Information section, click Backup Time and Advanced Settings.

   Note

   The following table describes the parameters that you need to set when you configure the backup time settings of a backup schedule. The parameters vary based on whether you select logical backup or physical backup as the backup method.

   Parameter	Description
   Full-scale Backup Frequency	The frequency of the backup schedule. Valid values: Periodic Backup and Single Backup. Note If you select Periodic Backup, you must set the Full Data Backup Recurrence and Start At parameters.
   Full Data Backup Recurrence	The days of the week on which DBS runs the backup schedule. You can select one to seven days of the week. Select at least one day of the week. Note DBS first performs a full backup in each week, and then performs incremental backups for the subsequent backups.
   Start At	The start time of the backup. We recommend that you set a point in time within off-peak hours. Example: 01:00. Note If a previous full data backup is not finished at the start time of the next backup, DBS skips the next backup.
   Incremental Backup	Specifies whether to enable the incremental backup feature. This parameter is displayed only if you set the Full-scale Backup Frequency parameter to Periodic Backup. Note Before you enable the incremental backup feature, make sure that the binary logging feature is enabled for the database that you want to back up. By default, the binary logging feature is enabled for an ApsaraDB RDS for MySQL database. If you use a self-managed database, you must manually enable the binary logging feature. For more information about how to enable the binary logging feature for a PolarDB for MySQL cluster, see Enable binary logging. DBS does not support incremental backup for Oracle, PolarDB for PostgreSQL (compatible with Oracle), PolarDB for Xscale (PolarDB-X), and PostgreSQL databases. By default, the incremental backup feature is disabled for a backup schedule that is purchased to back up files and cannot be enabled.
   Maximum Concurrent Threads for Full Data Backup	The maximum number of concurrent threads that are available for a full backup. You can set this parameter to adjust the backup speed. For example, you can reduce the number of backup threads to minimize impacts on the database. The maximum number of actual concurrent threads varies based on backup schedule specifications. For more information, see How do I change the maximum backup speed?
   Backup network speed limit	The limit on the network bandwidth. Unit: MB/s. You can set the limit based on your business requirements. Default value: 0, which indicates that the network bandwidth is unlimited. Note When you back up the production database, we recommend that you configure throttling for the backup to reduce impacts on the production database.
   Read speed limit	The limit on the disk I/O. You can set the limit based on your business requirements. Default value: 0, which indicates that the disk I/O is not limited. Note This parameter is displayed only if you specify the physical backup method for a MySQL database.
   Incremental Backup Interval	The interval at which an incremental backup is performed. If you set the interval to 10 minutes, DBS performs an incremental backup every 10 minutes. Note This parameter is displayed only if you set the Incremental Backup parameter to Enable.
   Does not automatically delete backed up incremental	Specifies whether not to automatically delete the archived redo log files that are backed up. Valid values: Enable: DBS does not automatically delete the archived redo log files that are backed up. Disable: DBS automatically deletes the archived redo log files that are backed up. By default, the archived redo log files that were backed up seven days ago are deleted. Note This parameter is displayed only if you specify the physical backup method for an SQL Server database. If you want to modify the default retention period of the archived redo log files that are backed up, contact technical support. For example, you can contact technical support to help you change the retention period to 14 days.
   Delete Logs upon Backup Success	Specifies whether to automatically delete the archived log files that are backed up from a self-managed database. Valid values: Enable: DBS automatically deletes the log files archived prior to the time specified by the archive log save days parameter from a self-managed database after a successful backup. Default value of the archive log save days parameter: 7. If you set this parameter to the default value, DBS automatically deletes the log files archived seven days ago from a self-managed database after a successful backup. Disable: DBS does not automatically delete the archived log files that are backed up from a self-managed database. Note This parameter is displayed only if you specify a physical backup method or a true incremental-forever backup method for an Oracle database.
   archive log save days	Specifies that DBS automatically deletes the log files archived before this period from a self-managed database after a successful backup. Default value: 7. If you set this parameter to the default value, DBS automatically deletes the log files archived seven days ago from a self-managed database after a successful backup. Note This parameter is displayed only if you set the Delete Logs upon Backup Success parameter to Enable.
   Enable compression	Specifies whether to enable compression during a backup. Valid values: Enable: recommended. Data is compressed during a backup to reduce storage space. Disable: Data is not compressed during a backup.
   Compression algorithm	The algorithm that is used to compress data. Valid values: GZIP (default) LZ4 Note This parameter is displayed only if you set the Enable compression parameter to Enable.
   Backup set mode	The method that is used to back up the database. Valid values: Non-intrusive streaming backup: DBS uses Oracle System Backup to Tape (SBT) to back up data. Backup data is stored as backup sets on a virtual tape before the data is streamed to the cloud. This method requires less storage space and does not have a negative impact on the source database. Sandbox instance mount backup: DBS uses the Recovery Manager (RMAN) tool to perform image copy backup. Backup data is streamed and sent to Object Storage Service (OSS) by using the Filesystem in Userspace (FUSE) protocol, instead of being stored on disks. After the sandbox feature is enabled, the backup data can be mounted within seconds. Note This parameter is displayed only if you specify a physical backup method or a true incremental-forever backup method for an Oracle database. You must install FUSE on your server to ensure successful data backups. To create a true incremental-forever backup for an Oracle database, you must set this parameter to Sandbox instance mount backup.

4. Click Save.