Database Backup (DBS) supports backup and restore for Oracle Real Application Clusters (RAC) databases. DBS provides the features of remote backup, long-term archiving, compressed storage, and encryption.
Background information
In an Oracle RAC environment, multiple database instances share the same set of files, including control files, SPFILEs, data files, archived log files, and redo log files. Generally, these files are managed on an Alibaba Cloud Service Mesh (ASM) instance. This ensures that each database instance in the environment can access all the data. Before you back up an Oracle database in an Oracle RAC environment, you must check the locations of the preceding files in the environment and make sure that the files are accessible. For more information, see Query file locations in an Oracle RAC environment.
Features
Feature | Description |
---|---|
Remote backup | DBS supports backup of an Oracle instance to a database on the cloud of another region. DBS allows you to restore the backup data to a standalone instance in a data center or a database on the cloud. |
Long-term archiving | DBS can retain your backup data for up to five years. After the five years, DBS automatically transfers the backup set to Archive Storage. |
Backup speed limit | DBS allows you to limit the backup speed to reduce the negative impact of backup operations on the database performance. |
Compressed storage | DBS supports native compression schemes of Oracle databases and the LZ4 compression algorithm. |
Streaming backup | DBS directly writes the backup data to Object Storage Service (OSS) without storing the data on a local disk first. |
Encryption | DBS uses HTTPS encryption to transfer data, and AES-256 encryption to store data. |
Create a backup schedule
Configure the backup schedule
View the backup schedule
Restore an Oracle RAC database
Query file locations 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 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 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 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 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.