Oracle Database Appliance (ODA): Backing Up Oracle Databases on ODA to Oracle Cloud

Asset ID:	1-79-2123358.1
Update Date:	2016-05-31
Keywords:

Solution Type Predictive Self-Healing Sure

Solution 2123358.1 : Oracle Database Appliance (ODA): Backing Up Oracle Databases on ODA to Oracle Cloud

Applies to:

Oracle Database Appliance - Version All Versions to All Versions [Release All Releases]
Linux x86-64

Purpose

This document details the steps required to backup Oracle databases running on ODA to Oracle Cloud.

Details

NOTE:You need subscription or trial account for Oracle Database Backup Cloud Service or Oracle Storage Cloud Service.

STEPS:

1. Download the Oracle Cloud Backup Module (OCBM) from OTN:

http://www.oracle.com/technetwork/database/availability/oracle-cloud-backup-2162729.html

2. Copy the 'opc_install.zip' file to the ODA server.

3. Unzip the 'opc_install.zip' file on the ODA server. It will extract 2 files:

   [oracle@myoda1n1 tmp]$ unzip opc_installer.zip
   Archive: opc_installer.zip
   inflating: opc_install.jar
   inflating: opc_readme.txt

4. Install Oracle Cloud Backup Module using the following command.

[oracle@myoda1n1 ~]$ java -jar /tmp/opc_install.jar -serviceName Storage -identityDomain usoracle07396 -opcId <userid> -opcPass <password> -l -walletDir $ORACLE_HOME/dbs/opc_wallet -libDir $ORACLE_HOME/lib
Oracle Database Cloud Backup Module Install Tool, build 2016-02-04
Oracle Database Cloud Backup Module credentials are valid.
Oracle Database Cloud Backup Module wallet created in directory /u01/app/oracle/product/12.1.0.2/dbhome_1/dbs/opc_wallet.
Oracle Database Cloud Backup Module initialization file /u01/app/oracle/product/12.1.0.2/dbhome_1/dbs/opcproddb1.ora created.
Downloading Oracle Database Cloud Backup Module Software Library from file opc_linux64.zip.
Downloaded 26933594 bytes in 112 seconds. Transfer rate was 240478 bytes/second.
Download complete.

NOTE: If ORACLE_HOME & ORACLE_SID is not set when running the above command, please specify the "-configFile" option to explicitly provide the name of the initialization parameter file that will be created. For a complete list of available options, please review the 'opc_readme.txt' file extracted in step 3.

The installation of the OCBM does the following:

Creates the configuration file under $ORACLE_HOME/dbs.
Installs the library file (libopc.so).
Creates the auto-login Wallet using the Cloud Service credentials.

5. Configure RMAN Settings.

[oracle@myoda1n1 ~]$ echo $ORACLE_SID
proddb1
[oracle@myoda1n1 ~]$ rman target /

Recovery Manager: Release 12.1.0.2.0 - Production on Fri Apr 1 09:43:10 2016

connected to target database: PRODDB (DBID=647811132)

RMAN> configure channel device type sbt
2> parms='SBT_LIBRARY=libopc.so ENV=(OPC_FILE=/u01/app/oracle/product/12.1.0.2/dbhome_1/dbs/opcproddb1.ora)';

using target database control file instead of recovery catalog
new RMAN configuration parameters:
CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS 'SBT_LIBRARY=libopc.so ENV=(OPC_FILE=/u01/app/oracle/product/12.1.0.2/dbhome_1/dbs/opcproddb1.ora)';
new RMAN configuration parameters are successfully stored

RMAN> show all;

using target database control file instead of recovery catalog
RMAN configuration parameters for database with db_unique_name PRODDB are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO '%F'; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 5 BACKUP TYPE TO BACKUPSET;
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS 'SBT_LIBRARY=libopc.so ENV=(OPC_FILE=/u01/app/oracle/product/12.1.0.2/dbhome_1/dbs/opcproddb1.ora)';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE ON;
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'MEDIUM' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
CONFIGURE RMAN OUTPUT TO KEEP FOR 7 DAYS; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/fast_recovery_area/datastore/proddb/snapcf_proddb.f';

6. Enable Encryption For RMAN Backups (required).

If you are using an Oracle Wallet (called Keystore in Oracle 12c), you can configure encryption in RMAN settings so that all backups are encrypted.

RMAN> CONFIGURE ENCRYPTION FOR DATABASE ON;

If Oracle Wallet is not configured, enable the password encryption using the following command in each RMAN session.

RMAN> SET ENCRYPTION ON IDENTIFIED BY "<password>" ONLY';

If encryption is not enabled, RMAN backups to Oracle Cloud will fail with the following message:

ORA-27030: skgfwrt: sbtwrite2 returned error
ORA-19511: Error received from media manager layer, error text:
KBHS-01602: backup piece 06q9ddqb_1_1 is not encrypted

7. Enable Compression (optional).

Optionally, you can enable RMAN backup compression. MEDIUM compression is recommended.

RMAN> CONFIGURE COMPRESSION ALGORITHM 'MEDIUM';

8. Once these settings are in place, you can perform the RMAN backup as desired. For example:

RMAN> SET ENCRYPTION ON IDENTIFIED BY 'mypassw0rd' ONLY;

executing command: SET encryption

RMAN> BACKUP DEVICE TYPE SBT AS COMPRESSED BACKUPSET DATABASE PLUS ARCHIVELOG FORMAT '%U';

References

<NOTE:1640149.1> - Oracle Database Backup Service - FAQ

Attachments

This solution has no attachment