Use this procedure to update the backup schedule and advanced settings for an existing backup plan in Database Backup Service (DBS).
Prerequisites
Before you begin, ensure that you have:
Created a backup plan
Configured the backup plan
Update backup settings
Log on to the DMS console V5.0.
In the top navigation bar, choose Security and Specifications (DBS) > Data Disaster Recovery (DBS) > Backup Plan.
In simple mode, move the pointer over the
icon in the upper-left corner and choose All Features > Security and Specifications (DBS) > Data Disaster Recovery (DBS) > Backup Plan.Find the backup plan you want to update, then click Manage in the Actions column. The Configure Backup Job page appears.
In the Basic Information section, click Backup Time and Advanced Settings.
Configure the parameters. See the parameter reference below.
Click Save.
Parameter reference
The parameters available depend on your backup type (logical or physical) and database engine. Parameters shown in the console take precedence over descriptions in this table.
Some parameters are conditional—they appear only when a specific backup type or database engine is selected. The tables below group parameters by function and note visibility conditions where applicable.
Backup schedule
| Parameter | Description |
|---|---|
| Full Backup Frequency | Select Periodic Backup for recurring backups on a set schedule, or Single Backup for a one-time backup. Selecting Periodic Backup also requires you to configure Full Backup Cycle and Full Backup Start Time. |
| Full Backup Cycle | Select the days of the week to run full backups. You can select any day from Monday to Sunday. Select at least one day. DBS runs one complete full backup per week; the remaining scheduled backups are synthetic incremental backups. |
| Full Backup Start Time | Select the time to start the backup (for example, 01:00). Schedule backups during off-peak hours to reduce the impact on your database. If a previous backup job is still running at the scheduled time, the current backup is skipped automatically. |
| Incremental Backup | Enable to run incremental backups between full backups. Displayed only when Full Backup Frequency is set to Periodic Backup. See Incremental backup requirements and limitations. |
| Incremental Backup Interval | Specify how often incremental backups run. For example, setting this to 10 minutes runs an incremental backup every 10 minutes. Displayed only when Incremental Backup is set to Enable. |
Incremental backup requirements and limitations
Binary logging (binlog) must be enabled on the database. Binlog is enabled by default for RDS for MySQL. For self-managed MySQL databases, enable it manually. 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, incremental backup is disabled and cannot be enabled.
Performance and throttling
| Parameter | Description |
|---|---|
| Maximum Number Of Parallel Threads For Full Backup | Set the maximum number of parallel threads for full backups. Reduce this value to minimize the impact on your database during backup. |
| Backup Network Speed Limit | Set the network bandwidth throttling limit in MB/s. The default value is 0 (no limit). This value has no upper limit. Configure a limit for production databases to reduce the impact on workloads. |
| Backup Read Throttling | Set the disk I/O limit. The default value is 0 (no limit). This value has no upper limit. Displayed only for physical backups of MySQL databases. |
Compression
| Parameter | Description |
|---|---|
| Enable Compression | Select Enable (recommended) to compress backup data and reduce storage usage, or Disable to skip compression. |
| Compression Algorithm | Select the compression algorithm: GZIP (default) or LZ4. Displayed only when Enable Compression is set to Enable. |
Log retention (database-specific)
The following parameters appear based on database engine and backup type.
SQL Server — physical backups only:
| Parameter | Description |
|---|---|
| Do Not Automatically Delete Backed-up Incremental Data | Control whether backed-up archived logs are automatically deleted. Enable: logs are retained. Disable: logs from more than 7 days ago are deleted automatically. 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. |
Oracle — physical backups and permanent incremental backups only:
| Parameter | Description |
|---|---|
| Delete Logs After Backup Succeeded | Control whether archived logs are deleted from the self-managed database after a successful backup. Yes: deletes logs older than the number of days set in Delete Archived Logs Older Than (Days). No: retains all archived logs. |
| Delete Archived Logs Older Than (Days) | Specify the age threshold in days for deleting archived logs after a successful backup. The default is 7 days. Displayed only when Delete Logs After Backup Succeeded is set to Yes. |
Backup set mode (Oracle only)
Applies to physical backups and permanent incremental backups of Oracle databases. Permanent incremental backups support only the Sandbox Instance Mount Backup mode.
| Option | Description |
|---|---|
| Non-intrusive Stream Backup Mode | Backs up data using an Oracle SBT (backup set). Data streams to the cloud through a virtualized tape interface—non-intrusive to the source database and requires relatively little storage space. |
| Sandbox Instance Mount Backup | Performs an Image Copy backup using RMAN. Data is backed up to OSS through the FUSE file protocol and streamed directly to OSS without being written to disk. When the DBS sandbox feature is enabled, backup data can be mounted within seconds. FUSE must be installed on the server; otherwise, the backup fails. |
API reference
| API | Description |
|---|---|
| ModifyBackupStrategy | Modifies the backup time of a backup plan. |