RAC Subclient Properties (Backup Arguments)

RAC Subclient Properties (Advanced)

Use this tab to define the backup arguments of a new subclient or to change the backup arguments of an existing subclient.

The following tabs are displayed:


Use this tab to view or set the backup arguments for this subclient.

Data Files (BFS)

The number of data files to be bundled in each RMAN backup set. When a value is entered greater than the default setting of 32, the following line will be displayed in the RMAN log file: set limit channel ch1 maxopenfiles = nn;

Archive Files (BFS)

The number of archive files to be bundled in each RMAN backup set.

Max Open Files

Use this space to specify the maximum number of concurrent open datafiles that RMAN can read from simultaneously during a backup operation.


Define the RMAN backup set size.

  • Maximum Size

    The maximum size allowed for an RMAN backup set.

  • Section Size

    The size of each data file section used in an RMAN backup set for Oracle 11g backups.

Backup Tag

Use this space to enter a character string that will be used as the Oracle Tag argument associated with backups performed on the selected subclient.

Offline Arguments

The offline arguments are enabled when you choose Offline Databases in the Content tab.

Run Shutdown/Startup Script

Specifies whether the shutdown script will be automatically executed before backing up databases. This script shuts down the database and uses the SPFile to start up the database in mount mode. Once the backup is completed, the script opens the database. When cleared, you will have to manually start the database in mount mode, before performing a backup of an offline database. The lights out script is automatically installed with the Oracle RAC iDataAgent.

Broadcast Warning Message to Users

For Oracle RAC on UNIX, specifies whether to issue a message to the physical node for users logged into the database warning them that the database will be shut down in the number of minutes specified in the Delay Time (min) option.

Delay Time After Warning Message (Min)

For Oracle RAC on UNIX, use this space to specify the number of minutes that you want the system to wait after the warning message is sent to the physical node before attempting to shut down the database.

No. of Retriesr

Use this space, located below the Delay Time After Warning Message (Min) option, to specify the number of times that the system will retry attempts to shut down the database when the Delay Time After Warning Message (Min) option is activated.

Sleep Time Between Retries (Sec)

Use this space to specify the interval in seconds that you want the system to wait, or sleep, between retry attempts to shut down the database and check the status. Note that this option is only activated when the database cannot be shut down during the first attempt after the Delay Time After Warning Message (Min) has expired.

Use SQL Connect

When selected, the CommServe connects to the RAC database using the SQL command “Connect <Connect string> as sysdba”. The “Connect String” value is configured in the Instance properties (Details) tab. When not selected, the connection is established using the SQL command “Connect /as sysdba”.

Startup Parameter File (PFILE) Location

Specifies the location of the PFile to be used with the Run Shutdown/Startup Script option. You need to select this option only if you want to start up the database using the PFile. By default, the system uses the SPFile available in $ORACLE_HOME/dba directory (for UNIX) or $ORACLE_HOME/database directory (for Windows) to start up the database.


Click to establish or change the designated STARTUP PFILE.


Use this tab to view or set the auxiliary and common arguments for this subclient.

Auxiliary Arguments

  • Skip Read Only

    Specifies whether to omit read-only tablespaces from the backup.

  • SKIP Offline

    Specifies whether to omit offline tablespaces from the backup.

Common Arguments

  • Validate

    Specifies whether to run a validate backup job, which will cause RMAN to simulate a backup job for the purpose of determining whether the backup can be successfully restored.

  • Merge Incremental Image Copies

    When selected, SnapProtect allows you to create an image copy of a database, then regularly create incremental backups of the database and apply them to this image copy. The system will update the image copy with all the incremental changes that have taken place since the previous full using the System Change Number (SCN) . RMAN can use this updated datafile in media recovery in the same manner as it would use a regular full image copy taken at that SCN. This reduces the overhead of performing a full image copy of the database everyday.

  • Skip Inaccessible Data and Archive Redo Log Files

    Specifies whether to omit data files and archived redo log files that are inaccessible due to read I/O errors from the backup. When cleared, the backup fails when it encounters inaccessible data files and archived redo log files.

  • Resync Recovery Catalog

    Specifies whether the contents of the Recovery Catalog will be synchronized with the contents of the control file.