Data Management:Cross-cloud or self-managed Oracle physical backup and restore

Supported Oracle architectures

Single-instance, single-instance with Automatic Storage Management (ASM), Oracle Data Guard Physical Standby, and Oracle Real Application Cluster (RAC).

Limitations

Because Oracle physical backups in Data Recovery Service (DBS) rely on RMAN and control files to manage backup metadata, you must be aware of the following limitations to ensure the reliability of backups and restores when you use DBS to perform an Oracle physical backup or restore:

• Configuring multiple backup schedules for the same Oracle database may cause restore failures.

• When performing a point-in-time restore, do not delete the latest full backup set that precedes the restore point.

Step 1: Create a backup schedule

For more information, see Create a backup schedule.

Step 2: Configure the backup schedule

1. Log on to the Data Management Service (DMS) console.

2. In the top navigation bar, choose Security and disaster recovery (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 disaster recovery (DBS) > Data Disaster Recovery (DBS) > Backup Plan.

3. Find the target backup schedule by its Backup Schedule ID, and click Configure Backup Schedule in the Actions column.

4. On the Configure Backup Source and Destination page, configure the backup source and destination, and then click Next.

   In the Backup Destination Information section, set Backup Storage Type to DBS Storage (Recommended) and Storage Mode to Encrypted Storage.

   Section	Parameter	Description
   N/A	Backup schedule name	Data Recovery Service (DBS) automatically generates a name. Specify a descriptive name for easy identification. The name does not need to be unique.
   Backup source	Backup method	The default value is the backup method that you selected when you created the backup schedule. This topic uses physical backup as an example.
   	Instance region	Select the region where your instance is located.
   	Backup gateway	Select the backup gateway for the source database. For information about how to add a backup gateway, see Add a backup gateway.
   	Database type	The default value is Oracle.
   	SID	Enter the Oracle SID of the source database. For more information, see Obtain the Oracle SID.
   	Database logon	Enter the SQL*Plus command to log on to the database in the format <username>/<password>@<instance_name> as sysdba. Example: sys/password@orcl as sysdba. Note You can also enter / as sysdba. However, if your database environment has disabled operating system authentication, the logon will fail. In this case, you must use the <username>/<password>@<instance_name> as sysdba format.
   	Oracle home	Enter the absolute path of ORACLE_HOME. For more information, see Obtain the database program directory. Note This parameter is optional.
   	Data cross-border compliance commitment	Read and select the compliance commitment checkbox.
   Backup destination	Backup storage type	The type of storage for the backup destination. Valid values: DBS Storage (Recommended): Data is automatically stored in DBS Storage. No separate storage space is required. Charges are based on the amount of data stored in DBS. For more information about the billing, see Storage fees. OSS For User: You must create a bucket in OSS in advance. For more information, see Create a bucket. Note This example uses DBS Storage. If you select User OSS, you must also configure the Object Storage Service (OSS) Bucket Name parameter. Only the OSS Standard storage class is supported. For large data volumes, purchasing a subscription DBS storage plan is more cost-effective for DBS Storage than pay-as-you-go billing.
   	Storage mode	The storage mode. Valid values: Encrypted (Recommended): Encrypts data at rest by using the industry-standard AES-256 algorithm. OSS supports server-side encryption. OSS encrypts the object upon upload and saves the encrypted version. When you download the object, OSS automatically decrypts it before returning it. For more information, see Server-side encryption. Non-encrypted: Encryption is not enabled.

5. On the Configure Backup Objects page, Back Up Entire Instance is selected by default. Click Next.

   Note

   When you back up an entire database, permissions, stored procedures, and other information are also backed up.

6. On the Configure Backup Time page, configure the backup time and other settings, and then click Next.

   Parameter	Description
   Full backup frequency	Select Periodic Backup or Single Backup as required.
   Full backup period	The days of the week on which DBS runs the backup schedule. You can select one or more days of a week. Select at least one day of the week.
   Full backup start time	The start time of the backup. We recommend that you specify a point in time during 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 incremental backup. Note To enable this parameter, ensure that archive mode is enabled for the source database. For more information, see Prerequisites. This parameter is displayed only when Full Backup Frequency is set to Periodic Backup.
   Maximum number of parallel threads for full backup	The maximum number of concurrent threads that are available for a full backup. You can configure this parameter to adjust the backup speed. For example, you can reduce the number of backup threads to minimize impacts on the database.
   Backup network speed limit	The limit on the network bandwidth. You can specify the limit based on your business requirements. Default value: 0, which indicates that the network bandwidth is not limited.
   Incremental backup interval	The interval at which incremental backup is performed. DBS performs incremental backup based on your configurations. If you set the interval to 10 minutes, DBS performs an incremental backup every 10 minutes.
   Delete logs after successful backup	Specifies whether to delete the successfully backed-up archive logs from the self-managed database. Valid values: Yes: After a successful backup, the system deletes archive logs that are older than a specific number of days. You must also configure the Delete Archive Logs Older Than (Days) parameter. The default value is 7 days, which means that after a successful backup, the system deletes archive logs older than 7 days from the self-managed database. No: Does not delete archive logs from the self-managed database.
   Enable compression	Specifies whether to enable compression. Valid values: Enable: recommended. Data is compressed during backup to reduce storage space. Disable: Data is not compressed during backup.
   Backup set mode	Select a backup mode. Valid values: Non-intrusive streaming backup: Performs backups by using the Oracle SBT (backup set) method. Data is streamed to the cloud through a virtual tape interface. This method is non-intrusive to the source database and uses less storage space. Sandbox instance mount backup: Performs an Image Copy backup by using RMAN. Backup data is backed up to OSS through the FUSE file protocol. Data is streamed to OSS without being written to local disks during the backup. If the sandbox feature is enabled, backup data can be mounted in seconds. Note Your server must have FUSE installed. Otherwise, the backup will fail.

7. On the Edit Lifecycle page, enter the retention period for full backup data in DBS Storage.

   If you enabled Incremental Backup in the previous step, you must also configure the retention period for incremental backup data. For more information about the backup data lifecycle, see Manage the lifecycle of backup data.

8. After the preceding configurations are complete, click Precheck in the lower-right corner of the page.

9. In the precheck dialog box, after the precheck passes, click Start Now.

   Note

   • The backup schedule is successfully configured once its Status changes to Running.

   • If an exception or error occurs with the backup schedule, troubleshoot and fix the issue promptly. For more information, see Fix an abnormal backup schedule. If the issue persists, contact customer support (DingTalk group ID: 35585947).

FAQ

Q: Can I back up an Oracle database to different regions simultaneously for multi-region storage?

A: The backup feature of Data Recovery Service (DBS) is managed by RMAN, and RMAN's metadata structure does not support this configuration. Therefore, you cannot back up a database to different regions simultaneously.