Advanced Configuration - Oracle RAC iDataAgent

Oracle RAC instances are created as part of the procedure to create a RAC pseudo-client. Multiple Oracle iDataAgent instances can be configured using a RAC pseudo-client. You can create one Oracle RAC instance per Oracle RAC node. See Creating a RAC Client for more information.

At least one Oracle iDataAgent instance must be configured within each Oracle RAC instance, and you cannot remove an Oracle iDataAgent instance from an Oracle RAC instance unless more than one Oracle iDataAgent instance is configured therein. Removing an Oracle iDataAgent instance from an Oracle RAC instance does not delete the backup data; this data is still available for restore by another eligible client. The Oracle User should have DBA and SYSDBA privileges for creating an Oracle RAC instance.

Manually Adding an Instance to the RAC Client

You can add a new instance to the existing RAC client. While adding a new instance make sure to use SYS login as connect string to connect to the database. Make sure that the Connect String value does not include "/" when used with the Use SQL Connect option as RAC will have multiple nodes.

If you want to use a SCAN connect string for an instance, use connect string as: sys/sys@nodename:1521/service name of the database where, service name is the database name.

For Example: sys/sys@devrac11gr2-1.xyzcompany.com:1521/DEVRAC11.xyzcompany.com

Use the following steps to add an instance to the existing RAC client.

From the CommCell Browser, navigate to Client Computers | <RAC Client>.
Right-click the <instance>, and click the Details tab, and then click Add.
In the Instance Physical Client list, select the Instance Physical client name.
In the Instance (ORACLE SID) box, type the Instance name.
Click the Change User Account.
In the User Account box, type the user account name.
In the Enter Password box, type the password for the user account.
In the Confirm Password box, type re-type the password for the user account.
Click OK.
In the Oracle Home box, type the Oracle installed path. Alternatively, you can click Browse to select the location.
In the Connect String box, type the Connect String (SYS login): <sys>/<syspassword>@<Oracle service>
Example: sys/password1@neworac1
In the TNX_ADMIN Folder box, type the TNX ADMIN folder name. Alternatively, click Browse to select the location.
Click the Storage Device tab, in the Storage Policy used for user command backup of data box, select a storage policy.
Click the Log Backup tab, in the Storage Policy used for all Archive Log backups box, select a storage policy name.
Click OK.

Configuring RAC One Node

In RAC one node configuration, a single instance of Oracle RAC database runs on one node of the cluster while the second instance is in a cold standby mode. If there is a failure or fault in the first node and the instance cannot be restarted on the same node, then RAC One Node detects it and relocates the instance to the second node. The benefit of this feature is that it automates the instance relocation without any downtime and manual intervention. In this configuration, you must use unique instance names while configuring instances on nodes. See Creating a RAC Client for more information. For example, if you have two RAC nodes and a database that is not relocated to node2, configure instance on node1 and node2. If instance is running on node1, instances on node1 must be instance_1. If a database is relocated to node2, then the instances on node2 will be instance_2.

For example:

If the RAC database name is testracdb.

Instances are testracdb_1 and testracdb_2.

If the node1 is active, the instances will be testracdb_1 on both nodes. If the database is relocated to node2, then the instances will be testracdb_2 on both nodes.

Use the following steps to configure the RAC on one node:

From the CommCell Browser, navigate to *Client Computers \| <RAC Client>. Right-click the <instance>, and click the Details* tab, and then click Add. In the Instance Physical Client list, select the Instance Physical client name. In the Instance (ORACLE SID) box, type the Instance name as testracdb_1 for Instance_1.
Type the Instance name as testracdb_2 for Instance_2
You will see the following warning message. Click OK.
In the Database Name box, type the name of the Oracle RAC database (testracd) to which you are assigning this client. In the Connect String box, type the Scan Connect String (SYS login): username/password@physical-nodename:1521/service name of the database where, service name is the database name. It is important to use the physical node name in the scan connect because the backup process requires pre-identified node for backup resource reservation. Examples: Node 1 Connect String: sys/password1@dbserve26:1521/testracdb Node 2 Connect String: sys/password1@dbserve27:1521/testracdb You must use local scan connect to configure RAC on one node in a multiple node environment. In the Oracle Home box, type the Oracle installed path. Alternatively, you can click Browse to select the location. In the TNS_ADMIN Folder box, type the TNS ADMIN folder name. Alternatively, click Browse to select the location. Click the Storage Device tab, in the Storage Policy used for user command backup of data box, select a storage policy. Click the Log Backup tab, in the Storage Policy used for all Archive Log backups box, select a storage policy name. Click OK.

See Can you restore from a RAC One Node in a multiple node configuration for important considerations that you need to follow while restoring from a RAC One Node.

Managing Subclients

The Oracle RAC iDataAgent is designed to back up and restore an Oracle RAC database (*.dbf) along with control files (*.ctl) and archived redo log files. After you create an Oracle RAC pseudo-client, a default subclient is created by the system only after you first configure an Oracle RAC database instance from the CommCell Console. Since an Oracle RAC instance references a RAC database, the default subclient includes the entire database associated with that instance. However, you can use the CommCell Console to create user-defined subclients to include only some of the database content by configuring the Subclient Properties (Content) tab. Any content that is not included in the user-defined subclients will remain in the default subclient.

You can create user-defined subclients to backup the specific components or conditions, such as the following:

Whether a backup will be offline or online.
Whether the entire database will be backed up, or only a subset of objects within the database should be backed up.
Whether the archive logs need to be backed up separately
Manage your archive log and control file backups.

If a new database object is added to the database, and if none of the subclients contain that database object , then that object is automatically assigned to the content of the default subclient.

Creating a Subclient for Offline Backups

During an offline backup, the database is shutdown and is not available for use. Since incremental backups require access to various tablespaces and datafiles, it is always recommended that you perform a full backup of the database when it is offline. The full backup includes all the datafiles, tablespaces, and control file of the Oracle database. Note that, offline backups do not include the archived log files.

Offline backups can be performed when the database is in offline or online mode. If the database is online, it shuts down the database, performs the backup and then brings up the database back.

In order to backup the Oracle database when it is offline, you need to create a separate user-defined subclient for offline backup. Make sure that the database is in the MOUNT mode during the backup.

Use the following steps to create a subclient for offline backups:

From the CommCell Browser, navigate to Client Computers | <RAC Client>.
Right-click the <Instance>, point to All Tasks, and then click New Subclient.
In the Subclient name box, type the subclient name.
Click the Content tab.
Click Offline Database.
Click the Storage Device tab.
In the Data Storage Policy box, select the storage policy name.
Click OK.

Creating a Subclient for Online Backups

In some environments, it may not be possible to bring down the entire database to perform an offline backup. In such situations, you can choose online backups, where the database will be up and running during the backup.

You can perform either a full backup or incremental backup of the Oracle database when it is online. Since full backups includes all the datafiles, tablespaces and logs, it is very time consuming, hence you can plan for a full online backup less frequently (say, on weekly basis). On the other hand, incremental backups includes the data and logs that have been changed after the last full backup, they are faster and can be performed more frequently (say, on a daily basis).

If a new database object is added to the database, and if none of the subclients contain that database object , then that object is assigned to the content of the default subclient

Use the following steps to create a subclient for online backups:

From the CommCell Browser, navigate to Client Computers | <RAC Client>
Right-click the <Instance>, point to All Tasks, and then click New Subclient.
In the Subclient name box, type the subclient name.
Click the Content tab.
Click Online Database.
Click the Storage Device tab.
In the Data Storage Policy box, select the Storage policy.
Click OK.

Creating a Subclient to Backup Individual Datafiles/Tablespaces

You can also create subclients to backup specific datafiles and tablespaces, which undergo frequent changes in the Oracle database.

Use the following steps to create a subclient to backup individual datafiles and tablespaces:

From the CommCell Browser, navigate to Client Computers | <RAC Client>.
Right-click the <Instance>, point to All Tasks, and then click New Subclient.
In the Subclient name box, type the subclient name.
Click the Content tab.
Click Online Subset.
Select the database objects to be included in the backup.
Click the Storage Device tab.
In the Data Storage Policy box, select the storage policy name.
Click OK.

Creating a Subclient for Log Backups

Archive logs are required to recover database transactions that have been lost due to an operating system or disk failure. You can apply these archive logs to an online backup in order to recover a database.

Though online full backups can include both data and logs, because of their importance in recovering data, it is recommended that you create separate subclients to backup archive log files.

From the CommCell Browser, navigate to Client Computers | <RAC Client>.
Right-click the <Instance>, point to All Tasks, and then click New Subclient.
In the Subclient name box, type the subclient name.
Click the Logs Backup tab.
Select the Backup Archive Log check box.
Click the Storage Device tab.
In the Data Storage Policy box, select the storage policy name.
Click OK.

Creating a Subclient for Selective Online Full Backups

You can selectively copy full backup to a selective copy during an auxiliary copy operation. The advantage of this type of backup is that both data and logs use the same storage policy, which means that they reside together on the same media. They are completely self-contained for restore and long term archiving purposes. Also, the data aging rules for selective online full backups are different from regular full backups, as both data and logs are aged together under the same storage policy

It is recommended to create a different storage policy during the creation of this subclient.

When performing the selective online full backup, note the following:

A selective online full backup job will wait for other Oracle backup jobs currently running on the same instance to complete before it begins.
For this type of backup, both data and archive logs will use the same storage policy as defined for data in the subclient, and will ignore the storage policy setting for archive logs (which is defined at the instance level).
During selective online full backups, if the data streams (defined at the subclient level) is less than the archive log streams (defined at the instance level), then both the data phase and the archive log phase will use the same number of streams defined for the data in the subclient, and will ignore the number of streams set for the archive logs.
While the data backup phase of a selective online full backup is running, the only other Oracle backup jobs that are allowed to run on the same instance are archive log backups. During the log backup phase of a selective online full backup, no other Oracle backups are allowed to run (neither logs nor data) on the same instance.
If other Oracle archive log backup jobs are running at the same time as the selective online full backup, they will be forced to use the same storage policy used by the selective online full backup during the time-frame in which the selective online full backup job is running, and will be included in the same auxiliary copy operation.

From the CommCell Browser, navigate to Client Computers | <RAC Client>.
Right-click the <Instance>, point to All Tasks, and then click New Subclient.
In the Subclient name box, type the subclient name.
Click the Content tab.
Select the Selective Online Full check box. Click OK on the warning message dialog box.
Click the Storage Device tab.
In the Data Storage Policy box, select the storage policy name.
Click OK.

Managing Control Files

As the Control file stores the status of the physical structure of the database. It is required when you want to recover the database to the current state. Hence it is important to include control files in your backups. By default, control files are included in the subclient for selective online full backups. You can also include/exclude control files for online or offline backups. The following sections describe the methods by which you can backup control files.

Enabling Automatic Backup of Control Files for All Subclients

You can configure the instance to automatically backup Control Files whenever you a backup the subclient in that instance.

Use the following steps to enable automatic backup of control files for all the subclients in the instance.

From the CommCell Browser, navigate to Client Computers | <RAC Client>.
Right-click the <Instance>.
Click the Details tab, in the Ctrl File Autobackup box,
- Select Configure ON. This will backup the control file separately.
- Alternatively, select Configure Off to backup the control file along with the datafile.
Click OK.

Enable/Disable Control File Backups for a Specific Subclient

If the control file backup is enabled at the instance level, you can also include/exclude control files for backups from a specific subclient. Use the following steps to enable control file backups for a specific subclient.

From the CommCell Browser, navigate to Client Computers | <RAC Client>| <Instance>.
Right-click the <Subclient>, and then click Properties.
Click the Content tab.
Select the Backup Control File check box.
Click OK.

Enabling Automatic Backup of the Control Files from RMAN

You can enable autobackup from RMAN command line to automatically backup the control file in every backup job operation.

Enter the following commands/parameters at the RMAN prompt (the catalog connect string is optional):

$rman target <connect string for target> catalog <connect string for catalog>RMAN>configure controlfile autobackup on;

For Example:$rman target systemuser/systempass@rman92 RMAN>configure controlfile autobackup on;

Configuring Table Restores

By default, all data is backed up which includes tablespaces. If you want to restore individual tables, you need to enable table level backup.

Enabling Table Browse for Restores

In order to backup and restore database tables, you need to enable table level backups for the subclient. Use the following steps to enable backups at table level.

From the CommCell Browser, navigate to Client Computers | <RAC Client> | <Instance>.
Right-click the <Subclient>, and then click Properties.
Click the Backup Arguments tab, and then click the Options tab.
Select the Enable Table Browse check box.
Click OK.

Setting Up the Auxiliary Instance

By default, when you restore database tables to a target instance, the system automatically duplicates the source database to an auxiliary instance in a temporary staging location specified during the restore operation. The database will be automatically imported from this auxiliary instance after the restore.

Use the following steps to set up a specific database as an auxiliary instance. This is useful when you want to restore a table to a specific failure point.

1. Copy the init<SID>.ora file from the source database to the auxiliary database instance.

2. Update the database name and the database file locations in the init<SID>.ora file for the auxiliary database instance.

3. Add the DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT parameters in the init<SID>.ora file. These parameters will redirect the datafiles, temp files, and log files to the auxiliary instance. Windows Clients:
DB_FILE_NAME_CONVERT=('source_of_df_path/','dup_of_df_path/',

'source_of_temp_path/','dup_of_temp_path/',...)

LOG_FILE_NAME_CONVERT=('source_of_log_path/

redo','dup_of_log_path/redo')

Unix Clients:

DB_FILE_NAME_CONVERT=(source_of_df_path/,dup_of_df_path/

,source_of_temp_path/,dup_of_temp_path/,...)

LOG_FILE_NAME_CONVERT=(source_of_log_path/redo,dup_of_log_path/redo)

4. Add the log_archive_dest_1 parameter is added to the init<SID>.ora file on the auxiliary instance.

5. Restart the Oracle Services, if using Windows clients.

6. Add the destination instance name in the Listener.ora and Tnsnames.ora files. If using a different host, add the duplicate database instance name in the Listener.ora file on the destination host and Tnsnames.ora files on the destination and source hosts. Also, add the original database name in the Tnsnames.ora file on the destination host. DUPDB = (DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = powerpc02)(PORT = 1521))

(CONNECT_DATA = (SERVER = DEDICATED)

(SERVICE_NAME = dupdb) (UR=A) ) )

7. Restart the Listener. $lsnrctl reload

8. Ensure that the auxiliary instance is in NOMOUNT mode. sql> startup nomount;

Configuring Archive Log Destinations

When you backup archive logs, you can specify the locations from where the log backups should be performed. This capability enables you to schedule backup operations from different log destinations on the same subclient. If necessary, you can also delete the logs after the backup.

Setting Up the Log Destination for Deletion

From the CommCell Browser, navigate to Client Computers | <RAC Client> | <Instance>.
Right-click the <Subclient>, and then click Properties.
Click the Log Destinations tab.
Select the Select ArchiveLog Destinations for Backup check box.
Click Add, type or select the Archive log file destination, and then click OK.
Click OK.

Deleting the Logs after a Backup

Ensure that the logs in the specified location are backed up. This may cause data loss if those archive logs are not backed up.

From the CommCell Browser, navigate to Client Computers | <RAC Client> | <Instance>.
Right-click the <Subclient>, and then click Properties.
Click the Log Destinations tab.
Select the Select ArchiveLog Destinations for Delete check box.
Click Yes to close the warning message.
In the Confirmation box, type confirm.
Click OK.
Click Add.
Type or select the Archive log file destination.
Click OK.
Click OK.

Disabling Log Switch

When performing archive log backups, the current redo log file is closed (even if it is not filled up completely) and the next redo log file is used for writing using a log switch. The closed redo log file is then archived during the log phase. Use the following steps to disable the log switch:

From the CommCell Browser, navigate to Client Computers | <RAC Client> | <Instance>.
Right-click the <Subclient>, and then click Properties.
Click the Content tab.
Clear the Data checkbox.
Click the Logs Backup tab.
Select the Backup Archive Log check box.
Select the Disable Switch Current Log check box.
Click OK.

Enabling Log Deletion after Backup

When backing up archive logs, by default the logs are not deleted after the backup operation. Use the following steps to enable deletion of logs soon after the backup.

From the CommCell Browser, navigate to Client Computers | <RAC Client> | <Instance>.
Right-click the <Subclient>, and then click Properties.
Click the Content tab.
Select the Archive Delete check box.
Click OK.

See Deleting Archive Logs After a Specific Backup for more information.

Changing the Oracle Home Directory

Oracle HOME directory refers to the location where the Oracle application resides. When instances are discovered, the home path is automatically assigned to the instance. However, you can modify the home path location for an instance at any point of time. Use the following steps to configure the Oracle HOME directory:

From the CommCell Browser, navigate to Client Computers | <RAC Client>.
Right-click the <Instance>, and then click Properties.
Click the Details tab, and select the desired RAC database instance, and then click Modify.
In the ORACLE HOME box, type the path to Oracle Home directory. Alternatively, you can use Browse to locate the path.
Click OK.

Changing the TNS ADMIN Directory

When an instance is configured, by default, the TNS_Admin directory is created in the Oracle HOME\network\admin path. Use the following steps to change the path for the TNS_ADMIN directory:

From the CommCell Browser, navigate to Client Computers | <RAC Client>.
Right-click the <Instance>, and then click Properties.
Click the Details tab.
Select the desired database instance, and then click Modify.
In the TNS_ADMIN folder box, type the location for the TNS Admin directory. Alternatively, you can use Browse to locate the path.
Click OK.

Configuring Lights Out Script for Offline Backups

In order to perform offline backups of the Oracle database, all users must be logged out of the database and it must be completely shut down. When the database is online, you can enable a graceful shutdown of the database using lights out script that will notify the users about the shutdown and set a specific wait time for the users to logout of the database. Use the following steps to configure lights out script for offline backups:

From the CommCell Browser, navigate to Client Computers | <RAC Client> | <Instance>.
Right-click the <Subclient>, and then click Properties.
Click the Content tab, and then click Offline Database.
Click the Backup Arguments tab, and then click the Offline Arguments tab.
Select the Lights Out Script check box.
Select the Warning checkbox to display a warning message on the physical node.
In the Delay Time box, select the delay time interval in minutes.
Select the Use SQL Connect checkbox to connect to the oracle database using the SQL command connect <connect string> as sysdba.
Click OK.

Including Server Parameter (SP) File During Backups

The Server Parameter file (SPFile) contains the database startup information. By default, the backups do not include the SPFile.

Use the following steps to include SPFile during backups:

From the CommCell Browser, navigate to Client Computers | <RAC Client> | <Instance>.
Right-click the <Subclient>, and then click Properties.
Click the Content tab.
Select the Back up SP FILE check box.
Click OK.

Enabling Backups of Flash Recovery Area

Flash Recovery Area is a specific area in the disk storage that exclusively holds a copy of all backup-related components, such as image copies, redo logs, and control file auto backups. This facilitates faster restores of backup data and minimizes restores from tapes during restore operations. Use the following steps to enable backup of flash recovery area:

From the CommCell Browser, navigate to Client Computers | <RAC Client> | <Instance>.
Right-click the <Subclient>, and then click Properties.
Click the Content tab.
Select the Protect backup recover area check box.
Click OK.

Configuring User Accounts for Backups

In order to perform backup and restore operations, you need to create and configure the following user accounts on the Oracle client:

User Account with administrative privileges to access the Oracle application.
On Unix clients, the user should be part of the user group assigned during the iDataAgent install. You can also use the operating system user account to verify the rights to perform all backup and restore operations for the associated Oracle instance.

On Windows clients, the user should be part of local administrator group and also part of the ora_dba group with read/write permissions on Calypso folder. You can use the Impersonate user account to verify the rights to perform all backup and restore operations for the associated Oracle instance.
User account to access the Oracle database. You can use separate accounts to access the standard database and the Recovery Catalog database. The account information is provided as a connect string with the following information:
- Database user ID.
- Password for the user ID.
- Oracle Service name.
The user account for standard database should have the following privileges:
- Administration privileges (default) or Oracle database administration privileges.
- SYSDBA and ALTER SYSTEM system privileges.
Alternatively, instead of using administrator user account with SELECT ANY TABLE privilege, you can also create user accounts with lesser privileges for accessing specific objects:

For example:
- SELECT ON "SYS"."V_$DATABASE"
- SELECT ON "SYS"."V_$DATAFILE"
- SELECT ON "SYS"."DBA_TABLESPACES"
- GRANT SELECT ON "SYS"."V_$ARCHIVE_DEST" TO "USER_NAME
The Recovery Catalog database user account must have recovery catalog owner privileges.

Additional accounts (except Impersonate User) should be established by Oracle database administrator.

Configuring User Account to Access the Oracle Application

Use the following steps to configure the user account to access the Oracle application:

From the CommCell Browser, navigate to Client Computers | <RAC Client>.
Right-click the <Instance>, and then click Properties.

Click the Details tab.
Select the desired Instance, and then click Modify.
On Windows clients:
- Click Change User Account.
- In the User Account box, type the user account name.
- In the Enter Password box, type the password for the user account.
- In the Confirm Password box, retype the password, and then click OK.
On Unix Clients:
- Click Change User Account.
- In the User Name box, type the user name, and then click OK.
Click OK.
Click OK.

Configuring User Account to access the Oracle Database

Use the following steps to configure the user account privileges to access the Oracle database:

From the CommCell Browser, navigate to Client Computers | <RAC Client>.
Right-click the <Instance>, and then click Properties.
Click the Details tab.
Select the desired Instance, and then click Modify.
In the Connect String box, type the connect string to connect to the Oracle database as following:
- Type the Database user ID.
- Click the Password box, in the Enter Password box, type the password for the user ID.
- In the Confirm Password box, retype the password, and then click OK.
- Type the Oracle service name.
For example:

sys/<password>@winrac1

where, sys is the Database User ID, <password> is the password of the Database User ID, and winrac1 is the Oracle service name.
Click OK.

Using Recovery Catalog for Backups

By default, recovery catalog is not used for backup and restore. As the recovery catalog contains metadata about RMAN operations for each registered database, it is recommended to include recovery catalog in backups. The metadata information is useful when you want to restore and recover the database after a crash. Use the following steps to use the Recovery Catalog for backups:

Verify that you have a recovery catalog database created using the following command:
From the CommCell Browser, navigate to Client Computers | <RAC Client>.
Right-click the <Instance>, and then click Properties.
Click the Details tab.
Select the Use Catalog Connect check box.
In the Catalog Connect string box, type the credentials to connect to the desired Recovery Catalog. For example, sys2/pwd34@orcl2

where sys2 is database user ID, pwd34 is password for the user ID and orcl2 is Oracle service name.
Click OK.

Synchronizing the Control File with the Recovery Catalog

It is a good practice to synchronize the recovery catalog with the control file, as the control file contains the latest backup information, which is need to perform restores.

Use the following steps to synchronize the control file with the recovery catalog:

From the CommCell Browser, navigate to Client Computers | <RAC Client>| <Instance>.
Right-click the <Subclient>, and then click Properties.
Click the Backup Arguments tab, and then click the Options tab.
Select the Resync Catalog check box.
Click OK.

Configuring Streams for Backups

The Oracle RAC iDataAgent allows you to perform parallel backups across multiple RAC nodes as a matter of design. Unlike other agents, this agent requires just one subclient and one storage policy per type used (i.e., data, log) along with the requisite number of allocated streams to perform parallel backups. As such, you can load-balance your backups across all or selected nodes of your RAC database and thereby take advantage of the strengths of each node.

Keep in mind that the same number of streams used for performing a backup will be needed to restore the data.

Data Backups

From the CommCell Browser, navigate to Client Computers | <RAC Client> | <Instance>.
Right-click the <Subclient>, and then click Properties.
Click the Storage Device tab.
Double click the Stream box of the desired instance, and then type or select the number of streams.
Click OK.

Log Backups

From the CommCell Browser, navigate to Client Computers | <RAC Client>.
Right-click the <Instance>, and then click Properties.
Click the Logs Backup tab.
Double click the Stream box of the desired instance, and then type or select the number of streams.
Click OK.

Enhancing Backup Performance

Several options are available for enhancing backup performance and reduce the network bandwidth used for performing backups. These options include:

Specifying the number of datafiles and archive files to be included in each RMAN backup set. The default value is 32.
Limiting the maximum size for each RMAN backup set. By default no limits are defined. By default no limits are defined.
Limiting the number of open datafiles that can be read by RMAN during the backup. The default value is 8.
Limiting the maximum size of data blocks used during backups. The default value is 262144 Kb.

In addition to the above configurations, you can also enable distribution of data across disks during backup operations. See Enhancing Backup Performance for more details

Use the following steps to enhance the backup performance:

From the CommCell Browser, navigate to Client Computers | <RAC Client> | < Instance>.
Right-click the <Subclient>, and then click Properties.
Click the Backup Arguments tab.
In the Data Files per BFS box, type or select the number of datafiles to be bundled in each RMAN backup set.
In the MAX Backup Set Size (kb) box, type or select the size of backup set allowed for RMAN backup set.
In the Archive Files per BFS box, type or select the number of archive files in each RMAN backup set.
In the Max Open Files box, type or select the number of datafiles that RMAN can read from simultaneously during a backup operation.

From the CommCell Browser, navigate to Client Computers | <RAC Client>.
Right-click the <instance>, and then click Properties.
Click the Details tab.
In the Block Size box, type or select the size of the block for backup and restore operations.
Click OK.

Assigning Unique Identification Tags for Backups

You can assign unique identification tags for all backup operations from a specific subclient. These tags can be used during a restore operation to easily identify a particular backup. Use the following steps to assign unique identification tag for backups.

From the CommCell Browser, navigate to Client Computers | <RAC Client> | <Instance>.
Right-click the <Subclient>, and then click Properties.
Click the Backup Arguments tab.
In the Oracle Tag box, type the tag name.
Click OK.

Excluding Data During Backups

You can configure a subclient to skip the following data during backup operations:

Read-only tablespaces
Offline tablespaces
Inaccessible Datafiles and Archived redo log files

Use the following steps to exclude data during backup operations:

From the CommCell Browser, navigate to Client Computers | <RAC Client> | <Instance>.
Right-click the <Subclient>, and then click Properties.
Click the Backup Arguments tab, and then click the Options tab.
Select the SKIP READ ONLY check box to exclude the read only tablespaces.
Select the SKIP OFFLINE check box to exclude the offline tablespaces.
Select the SKIP INACCESSIBLE check box to exclude inaccessible data and log files.
Click OK.

Simulating a Backup

Prior to running backup operations, you can check datafiles for physical and logical corruption.

Prior to running backup operations, you can validate a backup job, which will cause RMAN to simulate the backup for the purpose of determining whether the backup can be successfully restored. Once a validate job is completed, you can view the log files of the job to identify and correct any validation issues.

During validation, the backup jobs are simulated without the media, you can view the log files of the job to identify and correct any validation issues.

Use the following steps to enable validation of backup jobs:

Prior to running a backup, you can check the following:

Datafiles for physical and logical block corruption
Database files exist and are in the correct location.

From the CommCell Browser, navigate to Client Computers | <RAC Client> | <Instance>.
Right-click the <Subclient>, and then click Properties.
Click the Backup Arguments tab, and then click the Options tab.
Select the Validate check box.
Click OK.

Disabling the RMAN Crosscheck

By default, during a data aging operation, an Oracle CROSSCHECK is performed by the system to synchronize the entries in the CommServe database with the RMAN catalog. Use the following steps to disable the cross check operation:

From the CommCell Browser, navigate to Client Computers | <RAC Client>.
Right-click the <Instance>, and then click Properties.
Click the Details tab.
Select the Disable RMAN cross check check box.
Click OK to close the warning message.
Click OK.

Enabling Multiple Backup Copies

You can take multiple copies of the data or log backups using RMAN command line. During restores, even if one of the copies is missing or corrupted, the restore operation will automatically failover to the other copy and restore the data.

To utilize the PARALLELISM option, you need to set the initial parameter in pfile or spfile.

Example:

BACKUP_TAPE_IO_SLAVES=TRUE

Configure device type.

Example:

RMAN> CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO BACKUPSET;

Specify two copies of data.

Example:

RMAN> CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE 'SBT_TAPE' TO 2;

Specify two copies of log backups.

Example:

RMAN> CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE 'SBT_TAPE' TO 2;

Add the environmental variables for the client and instance on which the iDataAgent is installed.

Example:

allocate channel ch1 type 'sbt_tape'

PARMS="<software_install_path>/Base/libobk.so,

ENV=(CvClientName=<client_name>,

CvInstanceName=<instance_name>)"

Once you set the parameters, restart the Oracle database and perform backup operations from the CommCell Console.

Example: To restart the database,

Connect to the database.
SQL> connect admin/admin@orcl as sysdba
Shutdown the database.
SQL> shutdown
Mount the database.
SQL> startup mount;
Change to archivelog mode.
SQL> alter database archivelog;
Open the database.
SQL> alter database open;

Command Line Operations

You can add, modify, or delete several configurable properties for the Oracle RAC iDataAgent from the command line interface.

Command line configuration enables you to:

configure the same properties across multiple clients simultaneously.
reuse the same configurations for additional entities.

The following sections describe the available command line configurations:

Available Parameters

Parameter	Description of Parameter Values
appName	Name of the application. In this case it would be 'Oracle RAC'
clientName	Name of the RAC pseudo client as displayed in the CommCell Browser (eg., RACPseudoClient)
instancePhysicalClient/clientName	Name of RAC client node (eg., racnode1)
instanceName	Name of the Oracle instance (eg., dbname)
userAccount/userName	Name of the user that has local administrator rights to administer the Oracle application. This is the account used by the user to log in to and use the application to run jobs. (eg., oracle)
oracleRACInstance/connectString/userName	Name of the Oracle recovery catalog database (eg., cataloguser)
oracleRACInstance/connectString/password	Password for the catalog connect user (eg., catalogpasswd)
oracleRACInstance/connectString/serviceName	Name of the Oracle recovery catalog database (eg., catalogdb)
racDBInstance/connectString/userName	Name of the user with dba privileges (eg., sys)
racDBInstance/connectString/password	Password for the user with dba privileges
instanceOracleSID	Name of the RAC node database. (eg., dbname1 for racnode1 and dbname2 for racnode2)
oracleHome	Path for the Oracle application software (eg., /oracle/oraclehome/)
tnsAdminFolder	Path to the TNS Admin directory (eg., /oracle/oraclehome/network/admin/)
dataBackupStoragePolicy/storagePolicyName	Name of the data storage policy (eg., data_sp)
logBackupStoragePolicy/storagePolicyName	Name of the log storage policy (eg., log_sp)
blockSize	Block size value for backup and restore operations on the selected instance (eg., 163840)
enableDeduplication	Option to enable or disable deduplication. Valid values are True/False.
networkAgents	Number of Network Agents (eg., 2)
useCatalogConnect	Option to choose whether RMAN will use recovery catalog database at the time of backup. Valid values are True/False. If recovery catalog database need to be used choose true else false.
softwareCompression	Option to enable compression on the Client or MediaAgent computer. Valid values are: ON_CLIENT, to enable software compression on the client. ON_MEDIAAGENT, to enable software compression on the MediaAgent. USE_STORAGE_POLICY_SETTINGS, to use the software compression options defined on the storage policy. OFF, to disable software compression.

Log on to the Commserve

To run command line operations you must first login to the CommServe as follows:

From Command prompt, navigate to <Software_Installation_Directory>/Base and run the following command:
qlogin -cs <commserve name> -u <user name>
For example, to log on to CommServe 'server1' with username 'user1':
qlogin -cs server1 -u user1

Creating a RAC Pseudo Client

Download the CreateRACClient.xml file and save it on the computer from where the command will be executed.
From Command prompt, navigate to <Software_Installation_Directory>/Base and run the following command:
qoperation execute -af <xml_path>\CreateRACClient.xml -clientInfo/clientType 'RAC' -entity/clientName '<RACpseudoclientname>'

Adding First RAC Node

Download the CreateRACInstance.xml file and save it on the computer from where the command will be executed.
From Command prompt, navigate to <Software_Installation_Directory>/Base and run the following command:
qoperation execute -af <xml_path>\CreateRACInstance.xml -instance/appName 'Oracle RAC' -instance/clientName '<RACpseudoclientname>' -instance/instanceName '<RACinstancename>' -useCatalogConnect true -oracleRACInstance/connectString/userName '<catalog_db_user_name>' -oracleRACInstance/connectString/password '<catalog_db_password>' -oracleRACInstance/connectString/domainName '<catalog_db_name>' -ctrlFileAutoBackupType NOT_CONFIGURED -blockSize 163840 -disableRMAN true -networkAgents 2 -softwareCompression OFF -dataBackupStoragePolicy/storagePolicyName '<data_storage_policy>' -logBackupStoragePolicy/storagePolicyName '<log_storage_policy>' -enableDeduplication true -generateSignature ON_CLIENT -racDBOperationType ADD -instancePhysicalClient/clientName '<RACnode1name>' -instanceOracleSID <node1instancename> -userAccount/userName '<oracleusername>' -oracleHome '<oracle_home_path>' -racDBInstance/connectString/userName '<racdb_username>' -racDBInstance/connectString/password '<racdb_password>' -racDBInstance/connectString/serviceName '<racdbname>' -tnsAdminFolder '<tnsadmin_path>'

Adding Second RAC Node

Download the UpdateRACInstance.xml file and save it on the computer from where the command will be executed.
From Command prompt, navigate to <Software_Installation_Directory>/Base and run the following command:
qoperation execute -af <xml_path>\UpdateRACInstance.xml -instance/appName 'Oracle RAC' -instance/clientName '<RACpseudoclientname>' -instance/instanceName '<RACinstancename>' -racDBOperationType ADD -instancePhysicalClient/clientName '<RACnode2name>' -instanceOracleSID <node2instancename> -userAccount/userName '<oracleusername>' -oracleHome '<oracle_home_path>' -racDBInstance/connectString/userName '<racdb_username>' -racDBInstance/connectString/password '<racdb_password>' -racDBInstance/connectString/ServiceName '<racdbname>' -tnsAdminFolder '<tnsadmin_path>'

Getting RAC Instance Properties

Download the GetRACInstance.xml file and save it on the computer from where the command will be executed.
From Command prompt, navigate to <Software_Installation_Directory>/Base and run the following command:
qoperation execute -af <xml_path>/GetRACInstance.xml -appName 'Oracle RAC' -clientName '<RACpseudoclientname>' -instanceName '<RACinstancename>'

Click here to see a Sample Output

Modifying RAC Instance properties

Download the UpdateRACInstance.xml file and save it on the computer from where the command will be executed.
Execute the following command from the <Software_Installation_Directory>/Base folder after substituting the parameter values.
qoperation execute -af <xml_path>\UpdateRACInstance.xml -instance/appName 'Oracle RAC' -instance/clientName '<RACpseudoclientname>' -instance/instanceName '<RACinstancename>' -racDBOperationType OVERWRITE -instancePhysicalClient/clientName '<RACnodename>' -instanceOracleSID <instancename_for_node> -userAccount/userName <username> -oracleHome '<homepath>' -racDBInstance/connectString/userName '<connect_string_username>' -racDBInstance/connectString/password '<connect_string_password>' -racDBInstance/connectString/ServiceName '<connect_string_name>' -tnsAdminFolder '<tnsadmin_path>'

Deleting RAC Instance

Download the DeleteRACInstance.xml file and save it on the computer from where the command will be executed.
Execute the following command from the <Software_Installation_Directory>/Base folder after substituting the parameter values.
qoperation execute -af <xml_path>DeleteRACInstance.xml -appName 'Oracle RAC' -clientName '<RACpseudoclientname>' -instanceName '<RACinstancename>'

Examples

Creating a RAC Client	qoperation execute -af C:\XML\CreateRACClient.xml -clientInfo/clientType 'RAC' -entity/clientName 'RacPseudoClient'
Adding First RAC Node	qoperation execute -af C:\XML\CreateRACInstance.xml -instance/appName 'Oracle RAC' -instance/clientName 'RacPseudoClient' -instance/instanceName 'dbname' -useCatalogConnect true -oracleRACInstance/connectString/userName 'cataloguser' -oracleRACInstance/connectString/password 'catalogpasswd' -oracleRACInstance/connectString/domainName 'catalogdb' -ctrlFileAutoBackupType NOT_CONFIGURED -blockSize 163840 -disableCATALOGUSER true -networkAgents 2 -softwareCompression OFF -dataBackupStoragePolicy/storagePolicyName 'data_sp' -logBackupStoragePolicy/storagePolicyName 'log_sp' -enableDeduplication true -generateSignature ON_CLIENT -racDBOperationType ADD -instancePhysicalClient/clientName 'racnode1' -instanceOracleSID dbname1 -userAccount/userName 'oracle' -oracleHome '/oracle/oraclehome/' -racDBInstance/connectString/userName 'sys' -racDBInstance/connectString/password 'syspasswd' -racDBInstance/connectString/serviceName 'dbname1' -tnsAdminFolder '/oracle/oraclehome/network/admin/'
Adding First RAC Node without Catalog Connect	qoperation execute -af C:\XML\CreateRACInstance.xml -instance/appName 'Oracle RAC' -instance/clientName 'RacPseudoClient' -instance/instanceName 'dbname' -useCatalogConnect false -ctrlFileAutoBackupType NOT_CONFIGURED -blockSize 163840 -disableCATALOGUSER true -networkAgents 2 -softwareCompression OFF -dataBackupStoragePolicy/storagePolicyName 'data_sp' -logBackupStoragePolicy/storagePolicyName 'log_sp' -enableDeduplication true -generateSignature ON_CLIENT -racDBOperationType ADD -instancePhysicalClient/clientName 'racnode1' -instanceOracleSID dbname1 -userAccount/userName 'oracle' -oracleHome '/oracle/oraclehome/' -racDBInstance/connectString/userName 'sys' -racDBInstance/connectString/password 'oracle' -racDBInstance/connectString/serviceName 'dbname1' -tnsAdminFolder '/u01/app/oracle/product/11.2.0.3/db_1/network/admin/'
Adding Second RAC Node	qoperation execute -af C:\XML\UpdateRACInstance.xml -instance/appName 'Oracle RAC' -instance/clientName 'RacPseudoClient' -instance/instanceName 'dbname' -racDBOperationType ADD -instancePhysicalClient/clientName 'racnode2' -instanceOracleSID dbname2 -userAccount/userName oracle -oracleHome '/oracle/oraclehome/' -racDBInstance/connectString/userName 'sys' -racDBInstance/connectString/password 'passwd' -racDBInstance/connectString/ServiceName 'dbname2' -tnsAdminFolder '/oracle/oraclehome/network/admin/'
Configure Control File Auto Backup	qoperation execute -af C:\XML\UpdateRACInstance.xml -instance/appName 'Oracle RAC' -instance/clientName 'RacPseudoClient' -instance/instanceName 'dbname' -ctrlFileAutoBackupType CONFIGURE_ON
Set the Block Size	qoperation execute -af C:\XML\UpdateRACInstance.xml -instance/appName 'Oracle RAC' -instance/clientName 'RacPseudoClient' -instance/instanceName 'dbname' -blockSize 163840
Modify Log Storage Policy and Disable Catalog User	qoperation execute -af C:\XML\UpdateRACInstance.xml -instance/appName 'Oracle RAC' -instance/clientName 'RacPseudoClient' -instance/instanceName 'dbname' -logBackupStoragePolicy/storagePolicyName 'log_sp' -disableCATALOGUSER true
Change Network Agents	qoperation execute -af C:\XML\UpdateRACInstance.xml -instance/appName 'Oracle RAC' -instance/clientName 'RacPseudoClient' -instance/instanceName 'dbname' -networkAgents 2
Change Software Compression and Network Agents	qoperation execute -af C:\XML\UpdateRACInstance.xml -instance/appName 'Oracle RAC' -instance/clientName 'RacPseudoClient' -instance/instanceName 'dbname' -softwareCompression OFF -networkAgents 1
Enable Deduplication	qoperation execute -af C:\XML\UpdateRACInstance.xml -instance/appName 'Oracle RAC' -instance/clientName 'RacPseudoClient' -instance/instanceName 'dbname' -enableDeduplication true -generateSignature ON_MEDIAAGENT
Delete RAC Database Instance	Use the following command to delete the instance dbname1: qoperation execute -af C:\XML\UpdateRACInstance.xml -instance/appName 'Oracle RAC' -instance/clientName 'RacPseudoClient' -instance/instanceName 'dbname' -racDBOperationType DELETE -instancePhysicalClient/clientName 'racnode1' -instanceOracleSID 'dbname1'
Delete RAC Instance	qoperation execute -af <xml_path>DeleteRACInstance.xml -appName 'Oracle RAC' -clientName 'RacPseudoClient' -instanceName 'dbname'

Modifying an Agent, Instance, or Subclient

There are several configurable properties available for your agent that can be modified from the agent, instance, or subclient level as per need.

It is recommended that you do not modify the properties of a subclient when a job is in progress for that specific subclient. If a job is in progress, either wait for the job to complete or kill the job from the Job Controller.

The following table describes the properties that can configured from the agent, instance, and subclient levels.

Option	Description	Related Topics
Change Storage Policies	You can modify the storage policies in any of the following situations: To include a different media for the backup operation. To use a storage policy with a different retention criteria. You can change the storage policies from the subclient level. From the CommCell Browser, right-click the subclient. Click Properties. Click Storage Device. Select the Storage policy from the drop-down menu. Click OK.	Refer to Storage Policies.
Rename a Subclient	You can rename a subclient: From the CommCell Browser, right-click the subclient. Click Properties. Type the new name in the Subclient name field. Click OK.
Data Transfer Options	You can efficiently configure the available resources for transferring data secured by data protection operations from the subclient level. This includes the following: Enable or disable Data Compression either on the client or the MediaAgent. Configure the transfer of data in the network using the options for Network Bandwidth Throttling and Network Agents. You can configure the data transfer options. From the CommCell Browser,right-click the subclient. Click Properties. Click Storage Device. Click Data Transfer Option tab. Choose the appropriate software compression option for this subclient. Select Throttle Network Bandwidth and set the required bandwidth. Click OK.	Refer to Data Compression and Network Bandwidth Throttling.
View Data Paths	You can view the data paths associated with the primary storage policy copy of the selected storage policy or incremental storage policy. You can also modify the data paths including their priority from the subclient level. From the CommCell browser, right-click the subclient. Click Properties. Click Storage Device. Select Storage Policy from the drop-down menu. Click Data Paths.
Configure a Subclient for Pre/Post Processing of Data Protection	You can add, modify or view Pre/Post processes for the subclient. These are batch files or shell scripts that you can run before or after certain job phases. From the CommCell browser, right-click the subclient. Click Properties. Click Pre/Post Process. Click one of the following phases and type the full path of the process that you want to execute during that phase. Alternatively, click Browse to locate the process (applicable only for paths that do not contain any spaces). PreBackup Process PostBackup Process PreSnap Process PostSnap Process Click OK. Select Run Post Backup Process for all attempts to run a post backup process for all attempts. For subclients on Windows platforms, Run As displays Not Selected. If you want to change the account that has permission to run these commands, click Change. In the User Account dialog box, select Use Local System Account, or select Impersonate User and enter the user name and password. click OK. If you selected Local System Account, click OK to the message advising you that commands using this account have rights to access all data on the client computer.	Refer to Pre/Post Processes.
Configure Activity Control	You can enable backup and restore operations from the agent and subclient level. However, you can enable restore operations only from the agent level. From the CommCell browser, right-click the subclient. Click Properties. Click Activity Control, select or clear option(s) as desired. Click OK.	Refer to Activity Control.
Configure User Security	You can configure user security from the agent or subclient level. You can perform the following functions: Identify the user groups to which this CommCell object is associated. Associate this object with a user group. Disassociate this object from a user group. From the CommCell browser, right-click the subclient. Click Properties. Click Security. Select the appropriate user groups to which you want to associate to the CommCell object from the Available Groups pane, and then move the user group to the Associated Groups pane. Click OK.	Refer to User Administration and Security.
Enable/Disable Data Encryption	You can enable data encryption from the suclient level.Encryption must be enabled at the client level prior to configuring any instances residing on that client. From the CommCell browser, right-click the subclient. Click Properties. Click Encryption. Select the desired encryption. Click OK.	Refer to Data Encryption.
View Software Version and Installed Updates	The Version tab, at the Agent level displays the software version of the component. From the CommCell browser, right-click the agent. Click Properties. Click Version. Click OK.
CommCell Configuration Report	The CommCell Configuration Report provides the properties of the CommServe, MediaAgents, clients, agents, SRM agents, subclients, and storage policies within the CommCell based on the selected filter criteria. From the CommCell browser, click Reports icon. Select CommCell Configuration. Click Run.	Refer to CommCell Configuration.

Deleting an Agent, Instance, or Subclient

The following sections describe the steps involved in deleting an agent, instance, or subclient.

When you delete an instance or backupset, the associated data is logically deleted and you can no longer access the corresponding data from CommCell Console for recovery purposes.

Refer to the troubleshooting article on Recovering Data Associated with Deleted Clients and Storage Policies for information on how to recover data if you accidentally delete an entity.

Deleting an Agent

You need to uninstall or DeConfigure the agent software from the client computer before deleting from CommCell Browser. After you delete the client software, you can either leave the corresponding data intact for appropriate action or you can remove the data immediately. If you choose to remove the data immediately, you must delete the agent from the CommCell Browser. If you delete the agent, all of the agent's data is irretrievably lost.

You cannot delete an agent while operations for that agent are running.

From the CommCell Browser, navigate to Client Computers | <Client>.
Right-click the <Agent>, and then click Delete.
A confirmation message is displayed with the following message:
This operation will permanently delete the data backed up from this level and it cannot be restored.
Click OK to continue with the deletion operation., or click No to abort the deletion.

Deleting an Instance

Data that is backed up for any Oracle instance configured on the Oracle RAC node is lost if the configured Oracle instance is hard-deleted.

Consider the following before deleting an instance:

When you delete a specific instance all job schedules and job histories that pertain to any of the levels within the deleted instance are deleted.
You cannot delete an instance if it is being backed up. Attempts to delete an instance under such conditions cause the deletion to fail. If a backup is in progress, either wait for the backup to complete or kill the backup job using the Job Manager. Once the backup is no longer in progress, you can delete the instance level.
You cannot delete an instance if there is only one instance present for an agent. To delete the final instance, you must remove the agent software from the client computer.

From the CommCell Browser, right-click the instance that you want to delete, click All Tasks and then click Delete.
click Yes to confirm the deletion. (clicking No cancels the deletion and retains the node.)
Type the requested phrase in the Enter Confirmation Text dialog box and click OK. This should delete the instance.

Deleting a Subclient

Consider the following before deleting a subclient:

You cannot delete a default subclient.
Schedules associated with the subclient are also automatically deleted.

From the CommCell Browser, navigate to Client Computers | <RAC Client> | <Instance>.
Right-click the <Subclient> that you want to delete, and then click Delete.
A confirmation message is displayed, asking if you want to delete the subclient.
Click No to cancel the deletion and retain the subclient, or click Yes to continue the deletion.

1.	Copy the init<SID>.ora file from the source database to the auxiliary database instance.
2.	Update the database name and the database file locations in the init<SID>.ora file for the auxiliary database instance.
3.	Add the DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT parameters in the init<SID>.ora file. These parameters will redirect the datafiles, temp files, and log files to the auxiliary instance.	Windows Clients: DB_FILE_NAME_CONVERT=('source_of_df_path/','dup_of_df_path/', 'source_of_temp_path/','dup_of_temp_path/',...) LOG_FILE_NAME_CONVERT=('source_of_log_path/ redo','dup_of_log_path/redo') Unix Clients: DB_FILE_NAME_CONVERT=(source_of_df_path/,dup_of_df_path/ ,source_of_temp_path/,dup_of_temp_path/,...) LOG_FILE_NAME_CONVERT=(source_of_log_path/redo,dup_of_log_path/redo)
4.	Add the log_archive_dest_1 parameter is added to the init<SID>.ora file on the auxiliary instance.
5.	Restart the Oracle Services, if using Windows clients.
6.	Add the destination instance name in the Listener.ora and Tnsnames.ora files. If using a different host, add the duplicate database instance name in the Listener.ora file on the destination host and Tnsnames.ora files on the destination and source hosts. Also, add the original database name in the Tnsnames.ora file on the destination host.	DUPDB = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = powerpc02)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = dupdb) (UR=A) ) )
7.	Restart the Listener.	$lsnrctl reload
8.	Ensure that the auxiliary instance is in NOMOUNT mode.	sql> startup nomount;

Advanced Configuration - Oracle RAC iDataAgent

Table of Contents

Agent

Instance

Subclient

Examples