10
The configuration can be verified using the following command:
oracle@ita018[RAC1]:/home/oracle$ srvctl status service -d RAC -s BACKUP,MSL5000
Service BACKUP is running on instance(s) RAC1, RAC4, RAC3, RAC2
Service MSL5000 is running on instance(s) RAC1, RAC2
Oracle Online Backup Configuration
This section discusses topics such as Backup Session Failover and Backup Load Balancing.
In a large customer environment, hundreds of Oracle Databases are backed up daily. Backup
sessions have to run independently from the status of some of the RAC instances. While it is critical to
have regular backups for the availability of the data, it is also crucial to backup the archive logs on a
daily basis to avoid the archive log destination to fill up
The idea of Session Failover is to be able to have the backup session running although the configured
instance is not available. Session failover applies only to the start of the backup session and not to an
already running session.
Backup Load Balancing distributes the Backup Load over more than one RAC node. As a result, more
than one node will read the datafiles and write the data to tape. This is also valid for a Restore
Session.
Configuration Guidelines
The following is a list of the main tasks needed for the Oracle integration. It is only for reference and
does not replace the Data Protector Oracle online integration manual.
1.
Install the Data Protector Oracle agent on each and every RAC Node
2.
Add a root account has to the Data Protector Admin User group in the Users configuration
menu for every RAC Node and every virtual hostname.
1
(1)
3.
Add the oracle account to the Data Protector Admin User group in the Users configuration
menu for every RAC Node and every virtual hostname.
4.
Link the Oracle SBT library (located under $ORACLE_HOME/lib) with the Data Protector SBT
library on every node as oracle user. It can be done online (the link process is described in
the Data Protector Oracle integration documentation). This is step is not required in Data
Protector 6.1.
5.
Verity that the Oracle SQLNET connectivity works between each node and the RMAN
recovery catalog
6.
Optional: register database RAC in the recovery catalog (this step is done through the
Integration). The integration needs a database account with SYSDBA privileges. You can use
the Oracle Database built-in SYS account or you may prefer to create a new account (i.e.
dp_integration) and grant it SYSDBA (NOTE: the grant has to be done on each node of the
cluster).
7.
Import the Virtual IP Address (VIP) of every node in the RAC cluster; this will enable us to
configure the virtual IP as the client when doing the Integration.
1
A new enhancement has been developed, which doesn’t require the root account but only the oracle account is required. Contact your support
organization to receive the needed patch.
