Subclient Properties (Backup Arguments)
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 per BFS
Use this space to specify 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 per BFS
Use this space to specify the number of archive files to be bundled in each RMAN backup set.
Backup Set Size
Use this space to define the RMAN backup set size.
- Max Backup Set Size
Use this space to specify the maximum size allowed for an RMAN backup set.
- Section Size
Use this space to specify the size of each data file section used in an RMAN backup set for Oracle 11g backups.
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.
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.
The offline arguments are enabled when you choose Offline Databases in the Content tab.
Lights Out Script
Specifies whether the Lights Out Script will be automatically executed before backing up databases. This script shuts down the database and uses the SP file 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 iDataAgent.
For Oracle 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 (min)
For Oracle 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.
Sleep Time (min)
Use this space to specify the interval in minutes 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 number of tries limit has been reached for the Sleep Time (sec) option.
Use this space, located below the Sleep Time (min) option, to specify the number of times that the system will retry attempts to shut down the database when the Sleep Time (min) option is activated.
Sleep Time (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 (min) has expired.
Use this space, located below the Sleep Time (sec) option, to specify the number of times that the system will retry attempts to shut down the database when the Sleep Time (sec) option is activated.
Use SQL Connect
When selected, the CommServe connects to the oracle 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 PFILE location
Specifies the location of the PFile to be used with the Lights Out 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 SP file 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.
- SKIP READ ONLY
Specifies whether to omit read-only tablespaces from the backup.
- SKIP OFFLINE
Specifies whether to omit offline tablespaces from the backup.
- SKIP INACCESSIBLE
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.
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.
- Enable Table Browse
Specifies that the Oracle iDataAgent or Oracle RAC iDataAgent gathers the database tables and user information during the backup so that the backup data can be displayed in a table view during a browse operation. This option can be used only on subclients configured for online backups.
- Merge Incremental Image Copies
Specifies if the backups are incrementally updated backups. When this option is selected, an image copy of the database is created and the successive incremental backups will apply all the changes to the image copy up to the SCN of incremental backup and rolls them forward.
Merged incrementals help minimize the time required for media recovery of the database.
- Resync Catalog
Specifies whether the contents of the Recovery Catalog will be synchronized with the contents of the control file.