Instances - Oracle RAC

Overview

Oracle RAC instances are created as part of the procedure to create a RAC pseudo-client, and they are used to add, modify, and configure multiple Oracle iDataAgent instances. You can create one Oracle RAC instance per Oracle RAC node.

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. Also, 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.

See Instances for an overview of Instances. Given below is a list of what you need to provide before creating an Oracle RAC instance.

The Oracle User should have DBA and SYSDBA privileges
The name of the Oracle iDataAgent instance(s) that you want to include in the Oracle RAC instance along with the name of the associated physical client for each Oracle iDataAgent instance
The path to the Oracle home directory for each Oracle iDataAgent instance
Storage policy to be used by the default subclient for data for the Oracle RAC instance
Storage policies to be used by the instance for user command backups and archive log backups for the Oracle RAC instance
The database connect string for each Oracle iDataAgent instance
The catalog connect string for the catalog database for each Oracle instance
The path to the TNS Admin directory for each Oracle iDataAgent instance (optional)
The block size for backup and restore operations for each Oracle instance (optional)
The pass-phrase to enable data encryption for RMAN command line backups (optional)

Software compression for Oracle RAC Command Line Backups can be enabled or disabled at the instance level. Software compression for Oracle RAC Archive Logs Backups and data are managed through the subclient level. When you change the compression scheme for Archive Logs you change it for data as well, and vice versa.

You can also disable data compression by turning off both software and hardware compression.

Configurable Properties

Once created, the pseudo-client is configured, and the agent is therefore able to manage the data or volumes on the client computer. However, you can change certain aspects of the instance configuration to manage the data in the manner that best suits your needs.

You can view or change the instance configuration from the Instance Properties dialog box. The following information can be configured.

Change the Designated Home Directory

For the Oracle, Oracle RAC, and SAP for Oracle iDataAgents, you can change the Oracle Home directory. Similarly, you can change the Informix (Home) directory for the Informix iDataAgent, the Sybase Home directory for the Sybase iDataAgent, the MySQL Home directory for the MySQL iDataAgent, and the Instance Home directory for the DB2 DPF pseudo-client.

See Change the Home Directory for step-by-step instructions.

Change Connect Details

For the Oracle and Oracle RAC iDataAgents along with the Quick Recovery Agent with Oracle, you can view or change various settings of the selected instance (e.g., connect string, TNS Admin, block size for backups and restores, use of the Recovery Catalog database for backups, configure control file for autobackup). Some of these settings are also available for the SAP for Oracle iDataAgent. For Oracle, Oracle RAC and SAP for Oracle, see Change Instance Details for step-by-step instructions. For Quick Recovery Agent with Oracle, see Change Connect Details for step-by-step instructions.

Disabling RMAN Cross Check

For the Oracle and Oracle RAC iDataAgents, you can disable the synchronization of CommServe database entries with the RMAN catalog during a data aging operation. For more information, see Data Aging.

For step-by- step instructions on disabling the RMAN cross check, see Disable RMAN Cross Check.

Use Encryption for Third-party Command Line Operations

When accessing the Encryption tab from the instance level, you are selecting either Network and/or Media-side encryption for third-party Command Line operations. When accessing this same tab from the subclient level, the settings selected apply only to the selected subclient content for operations run from the CommCell Console. (See Data Encryption for an overview.) See the configuration section for your agent for more information on this feature.

View and Change Instance-level Storage Policies

From the Storage Device tab, you can view or change the storage policy used to back up data via the command line for the selected instance, select a storage policy for backing up logs on the selected instance, or view or select a default storage policy for the selected instance. By defining a storage policy for command line backups, you can view and track the status of those same jobs in the Job Controller. If you redefine (i.e., select a new) storage policy for command line backups at the instance level, the storage policy will apply only to any new command line backup jobs (i.e., those backup jobs that you subsequently start). (See Storage Policies for an overview.) See the configuration section for your agent for more information on this feature.

User Accounts

You can change the Windows or Unix user accounts that are used by the system to access the application and in effect perform all data protection and recovery operations for the iDataAgent.

See the Oracle iDataAgents section in User Accounts and Passwords for more information.

User Security

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.

For more information, see User Administration and Security.