Database backup (DBS) allows you to perform physical backup for single-instance Oracle databases, Data Guard Physical Standby databases, and Oracle Real Application Clusters (RAC) databases. You can restore the backup data to a different machine, a different directory of the source machine, or the same directory of the source machine.

Prerequisites

  • Your Oracle databases are deployed in Linux.
    Note If your Oracle databases are deployed in Windows, select logical backup to back up your data. For more information, see Back up an Oracle instance.
  • A backup gateway is installed on the server where your Oracle databases reside. For more information, see Add a backup gateway.

Oracle architectures that support physical backup

  • Single-instance Oracle databases
  • Automatic Storage Management (ASM)-based single-instance Oracle databases
  • Oracle Data Guard Physical Standby
  • Oracle RAC
    Note
    • To perform a successful backup, you must check the control files, SPFILEs, data files, archived log files, and redo log files of Oracle databases before you back up the data. For more information, see Query the locations of files in an Oracle RAC environment.
    • Data cannot be restored to Oracle RAC databases. Backup data can be restored only to single-instance Oracle databases.

Create a backup schedule

For more information, see Purchase a backup schedule.

Note When you purchase a backup schedule, set Database Type to Oracle and set Backup Method to Physical Backup.

Configure a backup schedule

  1. Log on to the DBS console.
  2. In the left-side navigation pane, click Backup Schedules. On the Backup Schedules page, select a region in the upper-left corner.
    Select a region
  3. On the Backup Schedules page, click Configure Backup Schedule in the Actions column corresponding to the backup schedule that you purchased.
  4. In the Configure Backup Source and Destination step of the Configure Backup Schedule wizard, configure the backup source and destination and click Next in the lower-right corner of the page.
    Note In this example, the physical backup mode is used. For information about how to back up an Oracle RAC database by using the logical backup mode, see Use DBS to back up an Oracle instance. In this step, you can install a backup gateway on the server of a database instance in the current Oracle RAC environment and then enter the system identifier (SID) of the Oracle database on this server. This way, all the Oracle databases in the current environment can be backed up.
    Section Parameter Description
    N/A Schedule Name The name of the backup schedule. DBS generates a backup schedule name. We recommend that you set a descriptive name that makes the backup schedule easy to identify. Backup schedule names do not have to be unique.
    Backup Source Information Backup Mode The method that is used to back up data. By default, the backup method that you selected when you purchased the backup schedule is used. In this example, the physical backup mode is used.
    Instance Region The region where the instance that you want to back up is deployed.
    Backup Gateway The backup gateway that is installed on the server where the database you want to back up resides. For more information about how to install a backup gateway, see Add a backup gateway. You can install the backup gateway on one of the multiple servers in the current Oracle RAC environment because all the database instances in the environment share the same data.
    Database Type The type of the database that you want to restore. Default value: Oracle.
    Whether to back up in the standby database Specifies whether the database that you want to back up is a primary database or a secondary database.
    Address The endpoint used to connect to the database that you want to back up.

    Default value: localhost. This parameter is available only when you set Whether to back up in the standby database to No.

    Port Number The port used to connect to the database that you want to back up.

    Default value: 1521. This parameter is available only when you set Whether to back up in the standby database to No.

    SID The SID of the Oracle database on the server where you want to install the backup gateway.

    This parameter is available only when you set Whether to back up in the standby database to No.

    Master Address The endpoint used to connect to the corresponding primary database.

    This parameter is available only when you set Whether to back up in the standby database to Yes.

    Master Port Number The port used to connect to the corresponding primary database.

    This parameter is available only when you set Whether to back up in the standby database to Yes.

    Primary SID The SID of the corresponding primary database.

    This parameter is available only when you set Whether to back up in the standby database to Yes.

    Standby SID The SID of the secondary database. The secondary database is the Oracle database on the server where you want to install the backup gateway.

    This parameter is available only when you set Whether to back up in the standby database to Yes.

    Master Database Account The username of the account that you can use to connect to the corresponding primary database.

    This parameter is available only when you set Whether to back up in the standby database to Yes.

    Master Password The password of the account that you can use to connect to the corresponding primary database.

    This parameter is available only when you set Whether to back up in the standby database to Yes.

    Backup Destination Information Backup Storage Type The type of storage of the backup data. Valid values:
    • DBS built-in storage (recommended)
    • OSS for user
    Note In this example, select DBS built-in storage (recommended). If you select OSS for user, you must set the OSS Bucket Name parameter.
    OSS Bucket Name The name of the OSS bucket.

    This parameter is available only when you set the Backup Storage Type parameter to OSS for user.

    Storage Encryption The method used to encrypt the stored data. Valid values:
  5. In the Edit Backup Objects step, Back Up Entire Instance is automatically selected. Click Next.
    Note If you back up an entire database, the permission data and stored procedures are also backed up.
  6. In the Configure Backup Time step, set the parameters as described in the following table and click Next.
    Parameter Description
    Full-scale Backup Frequency The frequency of the backup schedule. Valid values: Periodic Backup and Single Backup.
    Full Data Backup Recurrence The days of the week on which DBS runs the backup schedule.
    Full Data Backup Start At The start time of the backup. If the time required to complete a full data backup is longer than the backup interval, DBS skips the next backup.
    Incremental log real-time backup Specifies whether to enable incremental backup.
    Maximum Concurrent Threads for Full Data Backup The maximum number of concurrent threads available for a full data backup. The actual maximum number of concurrent threads varies based on backup schedule specifications.
    Transaction Log backup interval The interval at which incremental backups are performed. DBS performs incremental backups based on your setting. For example, if you set the interval to 10 minutes, DBS performs incremental backups every 10 minutes.
    Does not automatically delete backed up incremental Specifies whether to automatically delete archived log files that are backed up. Valid values:
    • Enable: Archived log files that are backed up are not automatically deleted.
    • Disable: Archived log files that are backed up seven days ago are automatically deleted.
    Note To retain your archived log files that are backed up for a different period of time other than seven days, submit a ticket. For example, you can submit a ticket to change the retention period to 14 days.
    Enable compression Specifies whether to compress data during backup. Valid values:
    • Enable: Data is compressed during backup to reduce storage space.
    • Disable: Data is not compressed during backup.
    Backup set mode The mode used to back up the database.
    • 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 uses less storage space and does not have a negative impact on the source database.
    • Mount backup in seconds: DBS uses Oracle disks to back up data. Backup data is stored as backup sets in a virtual disk before the data is streamed to the cloud. This method allows you to restore data in seconds and does not have a negative impact on the source database.
  7. In the Edit Lifecycle step, configure the lifecycle for a full data backup in the Configure Full Data Backup Lifecycle section.
    Note If you select Enable for the Real-Time Transaction Log Backup parameter, you must configure the backup time for incremental backup data.
  8. After the configuration is complete, click Precheck in the lower-right corner of the page.
  9. If the Precheck Passed message appears, click Start Task.
    Note When the status of the backup schedule changes to Running, the backup schedule takes effect.
    After data is backed up, you can view the backup schedule or restore the backup data. For more information, see View backup schedules and Restore Oracle databases.

Query the locations of files in an Oracle RAC environment

  • To query locations of redo log files, execute the following SQL statement:
    SELECT member FROM v$logfile WHERE type='ONLINE';
    The following figure shows a response. Each MEMBER entry starts with +. DBSBAKDAT1DG indicates the name of the ASM instance that is used to manage the files in the current Oracle RAC environment.
  • To query the locations of archived log files, execute the following SQL statement:
    SELECT name FROM v$archived_log WHERE DELETED='NO';
    The following figure shows a response.Each NAME entry starts with +. DBSBAKDAT1DG indicates the name of the ASM instance that is used to manage the files in the current Oracle RAC environment.
  • To query the locations of data files, execute the following SQL statement:
    SELECT name FROM v$datafile;
    The following figure shows a response. Each VALUE entry starts with +. DBSBAKDAT1DG indicates the name of the ASM instance that is used to manage the files in the current Oracle RAC environment.
  • To query the locations of SPFILEs, execute the following SQL statement:
    SHOW parameter spfile;
    The following figure shows a response. Each VALUE entry starts with +. DBSBAKDAT1DG indicates the name of the ASM instance that is used to manage the files in the current Oracle RAC environment.
  • To query the locations of control files, execute the following SQL statement:
    SELECT member FROM v$logfile WHERE type='ONLINE';
    The following figure shows a response.Each VALUE entry starts with +. DBSBAKDAT1DG indicates the name of the ASM instance that is used to manage the files in the current Oracle RAC environment.