Data Management:Modify the backup time and advanced settings

Procedure

1. Log on to the DMS console V5.0.

2. In the top navigation bar, choose Security and Specifications (DBS) > Data Disaster Recovery (DBS) > Backup Plan.

   Note

   If you use the DMS console in simple mode, move the pointer over the icon in the upper-left corner of the DMS console and choose All Features > Security and Specifications (DBS) > Data Disaster Recovery (DBS) > Backup Plan.

3. On the Backup Plan page, find the backup plan that you want to manage and click Manage in the Actions column. The Configure Backup Job page appears.

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

   Note

   The following table describes the parameters for setting the backup time for logical and physical backups. The parameters on the UI take precedence.

   Configuration	Description
   Full Backup Frequency	Select Periodic Backup or Single Backup based on your business needs. Note If you select Periodic Backup, you also need to configure Full Backup Cycle and Full Backup Start Time.
   Full Backup Cycle	Select the days of the week for data backup. You can select any day from Monday to Sunday. You must select at least one day per week. Note DBS performs a complete full backup once a week. The other backups are synthetic incremental backups.
   Full Backup Start Time	Select a start time for the backup, such as 01:00. We recommend that you set the start time to a time during off-peak hours. Note If a previous full backup job is still in progress at the specified backup time, the current backup is automatically skipped.
   Incremental Backup	Select whether to enable incremental backup. This parameter is displayed only when Full Backup Frequency is set to Periodic Backup. Note When you enable this parameter, make sure that binary logging (binlog) is enabled for the destination database. Binlog is enabled by default for RDS for MySQL. You must manually enable binlog for self-managed databases. To enable binlog for PolarDB for MySQL, see Enable binlog. Incremental backup is not supported for Oracle, PolarDB for PostgreSQL (Compatible with Oracle), PolarDB for Xscale, or PostgreSQL databases. For file backups, this feature is disabled and cannot be enabled.
   Maximum Number Of Parallel Threads For Full Backup	You can set the maximum number of parallel threads for a full backup to adjust the backup speed. For example, you can reduce the number of backup threads to minimize the impact on the database.
   Backup Network Speed Limit	Specify the network bandwidth throttling limit in MB/s. The default value is 0, which indicates no limit. This value has no upper limit. Note When you back up a production database, we recommend that you configure network bandwidth throttling based on your business needs to reduce the impact on the production database.
   Backup Read Throttling	Specify the disk I/O limit. The default value is 0, which indicates no limit. This value has no upper limit. Note This parameter is displayed only for physical backups of MySQL databases.
   Incremental Backup Interval	Specify the interval at which the system performs incremental backups. For example, if you set the interval to 10 minutes, the system performs an incremental backup every 10 minutes. Note This parameter is displayed only when Incremental Backup is set to Enable.
   Do Not Automatically Delete Backed-up Incremental Data	Select whether to automatically delete backed-up archived logs. Valid values: Enable: Does not automatically delete backed-up archived logs. Disable: Automatically deletes backed-up archived logs. By default, data from 7 days ago is deleted. Note This parameter is displayed only for physical backups of SQL Server databases. If you want to change the default deletion time, for example, to extend the data retention period by deleting data that is older than 14 days, contact technical support.
   Delete Logs After Backup Succeeded	Select whether to delete archived logs from the self-managed database after they are successfully backed up. The following options are supported: Yes: Deletes archived logs from the self-managed database that are older than a specified number of days after a successful backup. You must also configure the Delete Archived Logs Older Than (Days) parameter. The default value is 7, which means the system deletes archived logs that are older than 7 days. No: Does not delete archived logs from the self-managed database. Note This parameter is displayed only for physical backups and permanent incremental backups of Oracle databases.
   Delete Archived Logs Older Than (Days)	Specify the age in days for deleting archived logs from the self-managed database after a successful backup. The default value is 7, which means the system deletes archived logs that are older than 7 days. Note This parameter is displayed only when Delete Logs After Backup Succeeded is set to Yes.
   Enable Compression	Select whether to enable compression. The following options are supported: Enable (Recommended): Compresses data during backup to reduce storage space. Disable: Does not compress data during backup.
   Compression Algorithm	The following compression algorithms are supported: GZIP (Default) LZ4 Note This parameter is displayed only when Enable Compression is set to Enable.
   Backup Set Mode	Select the backup set mode. The following options are supported: Non-intrusive Stream Backup Mode: Backs up data using an Oracle SBT (backup set). Data is streamed to the cloud through a virtualized tape interface. This method is non-intrusive to the source database and requires relatively little storage space. Sandbox Instance Mount Backup: Performs an Image Copy backup using RMAN. The data is backed up to OSS through the FUSE file protocol. During the backup, the data is not written to disks but is streamed to OSS. If the DBS sandbox feature is enabled, the backup data can be mounted within seconds. Note This parameter is displayed only for physical backups and permanent incremental backups of Oracle databases. You must install FUSE on your server. Otherwise, the backup fails. Permanent incremental backup for Oracle supports only the sandbox instance mount backup mode.

5. After you complete the settings, click Save.