Advanced Backup - Oracle iDataAgent

Backups for any client start with a full backup. The full backup becomes a baseline to which subsequent backup types are applied. For example, a full backup must be performed before an archive log backup can be initiated.

You can perform a full backup of an online or offline database. If the database is in NOARCHIVELOG mode, you should perform offline backup only.

Use the following steps to run a full backup:

From the CommCell Browser, navigate to Client Computers | <Client> | Oracle | <Instance>.
Right-click the <Subclient> and click Backup.
Select Full as the backup type and click Immediate.
Click OK.
You can track the progress of the job from the Job Controller. When the backup job has completed, the Job Controller displays Completed.

Incremental Backups

Incremental backups can be performed when the database is online.

The incremental backups will fail if the database is offline.

An incremental backup contains only data that is new or has changed since the last backup, regardless of the type. On average, incremental backups consume less media and use less resources than full backups.

The illustration on the right clarifies the nature of full and incremental backups.

Follow steps given below to perform an incremental backup:

From the CommCell Browser, navigate to Client Computers | <Client> | Oracle | <Instance>.
Right-click the <Subclient> and click Backup.
Select Incremental as the backup type and click Immediate.
Click OK.
You can track the progress of the job from the Job Controller. When the backup job has completed, the Job Controller displays Completed.

Cumulative Incremental Backups

In a cumulative level n backup, all the data changes since the most recent backup at level n-1 or lower are backed up.

For example, in a cumulative level 2 backup, data changes since the most recent level 1 backup are backed up. If no level 1 backup is available, data changes since the base level 0 backup are backed up.

Cumulative incremental backups reduce restore times because you need one incremental backup from any particular level. However, cumulative backups require more space and time because they duplicate the work done by previous backups at the same level.

By default, the incremental level for cumulative backups is 1.

Follow the steps below to perform a cumulative incremental backup:

From the CommCell Browser, navigate to Client Computers | <Client> | Oracle | <Instance>.
Right-click the <Subclient> and click Backup.
Select Incremental as the backup type, and then type or select the incremental level in the Oracle Incremental Level box.
Select the Cumulative check box and click Immediate.
Click OK.
You can track the progress of the job from the Job Controller. When the backup job has completed, the Job Controller displays Completed.

Archive Log Backups

An archive log backup captures the archive redo logs generated during database transactions.

Archive log backups are useful when you want 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.

By default full backups include both data and archive logs. However, you can also perform separate archive log backups.

In order to perform a backup of the archive logs:

The database has to be in ARCHIVELOG mode.
Subclient should have been configured for archive log backups. See Creating A Subclient for Log Backups for step-by-step instructions to create a separate subclient for archive logs.

All Archive Logs

Use the following steps to backup all archive logs. Note that this is the default option:

From the CommCell Browser, navigate to Client Computers | <Client> | Oracle | <Instance>.
Right-click the <Subclient> configured for archive log backup, and then click Backup.
Click Advanced.
Click the Backup Archive Logs tab.

Click All.
Click OK.

By Number of Days

Use the following steps to backup archive logs older than a specified number of days.

From the CommCell Browser, navigate to Client Computers | <Client> | Oracle | <Instance>.
Right-click the <Subclient> configured for archive log backup, and then click Backup.
Click Advanced.
Click the Backup Archive Logs tab.

Click Older than n Days, and type or select the number of days older than which the archive logs are to be backed up.
For example, to backup logs older than 10 days, type 10.
Click OK.

Use the following steps to backup archive logs not older than a specified number of days.

From the CommCell Browser, navigate to Client Computers | <Client> | Oracle | <Instance>.
Right-click the <Subclient> configured for archive log backup, and then click Backup.
Click Advanced.
Click the Backup Archive Logs tab.

Click Not Older than n Days, and type or select the number of days not older than which the archive logs are to be backed up.
For example, to backup logs not older than 10 days, type 10.
Click OK.

Within a Specific Time Range

Use the following steps to backup archive logs between a specified time:

From the CommCell Browser, navigate to Client Computers | <Client> | Oracle | <Instance>.
Right-click the <Subclient> configured for archive log backup, and then click Backup.
Click Advanced.
Click the Backup Archive Logs tab.

Click By Log Time.
In the Time Zone box, select the time zone.
Select the Start Time check box and enter the start time after which the logs were generated.
Select the End Time check box and enter the time before which the logs were generated.
Click OK.

By Log Sequence Number

Log Sequence Number uniquely identifies an archive log. For example, if you create a database with two online log files, then the first file is assigned log sequence number 1. When the first file fills Oracle switches to the second file and assigns a log sequence number of 2; when it switches back to the first file, it assigns log sequence number 3, and so forth.

Use the following steps to backup archive logs within a specific range of log sequence numbers:

From the CommCell Browser, navigate to Client Computers | <Client> | Oracle | <Instance>.
Right-click the <Subclient> configured for archive log backup, and then click Backup.
Click Advanced.
Click the Backup Archive Logs tab.

Click By Log Seq Num.
Select the Start Seq Num check box and enter the start sequence number of logs to be backed up.
Select the End Seq Num check box and enter the end sequence number of logs to be backed up.
Click OK.

By System Change Number

System Change Number (SCN) is a stamp that defines a committed version of a database at a point in time. Oracle assigns every committed transaction a unique SCN. For example, SCNs of two successive transactions committed could be 576601 and 576799.

Use the following steps to backup archive logs within a specific range of system change numbers:

From the CommCell Browser, navigate to Client Computers | <Client> | Oracle | <Instance>.
Right-click the <Subclient> configured for archive log backup, and then click Backup.
Click Advanced.
Click the Backup Archive Logs tab.

Click By Sys change Num, and then specify the Start Sys Change Num and End Sys Change Num.
Click OK.

By a Specific String Pattern

Use the following steps to backup archive log files whose name match a specific naming pattern. Note that if you do not specify any pattern, all the logs from the specified destination will be backed up.

From the CommCell Browser, navigate to Client Computers | <Client> | Oracle | <Instance>.
Right-click the <Subclient> configured for archive log backup, and then click Backup.
Click Advanced.
Click the Backup Archive Logs tab.

Click Like, and then enter the desired string pattern in the text box.
For example, to backup all archive logs whose names start with 'arch' type 'arch%.log'.
Click OK.

From a Specific Location

Use the following steps to backup archive logs from a specific path or location. Note that the path or location specified at the backup level will override the archive log location defined at the subclient level.

From the CommCell Browser, navigate to Client Computers | <Client> | Oracle | <Instance>.
Right-click the <Subclient> configured for archive log backup, and then click Backup.
Click Advanced.
Click the Backup Archive Logs tab.

Click Like.
Select Select Archive Log Dest check box.
Click Add to select the archive log location.
Click OK.

Logs Not Backed Up a Specified Number of Times

Use the following steps to backup archive logs that have failed to backup a specified number of times earlier:

From the CommCell Browser, navigate to Client Computers | <Client> | Oracle | <Instance>.
Right-click the <Subclient> configured for archive log backup, and then click Backup.
Click Advanced.
Click the Backup Archive Logs tab.

Select the Not Backed Up n times check box, and type or select the number so that the logs that meet the criteria 'Not Backed Up n times' are backed up.
Click OK.

Deleting Archive Logs for a Specific Backup

Once the archive logs are backed up you can choose to delete them from the destination location. This can be done by configuring the subclient to delete archive logs soon after the backup. See Enabling Log Deletion After Backup for step-by-step instructions on enabling deletion of logs.

Always ensure that the archive logs are backed up before they are deleted to prevent data loss.

However, you can also choose to delete the archive logs for a specific backup job. Moreover, you can also specify additional criteria to delete the archive logs.

From the CommCell Browser, navigate to Client Computers | <Client> | Oracle | <Instance>.
Right-click the <Subclient> configured for archive log backup, and then click Backup.
Click Advanced.
Click the Delete Archive Logs tab.
Select the Delete Archive Log check box.
Click Yes on the warning dialog.
Type confirm in the Enter Confirmation text Dialog, and then click OK.

Specify the desired criteria for archive log deletion.

Click OK.

Control File Backups

The control file contains metadata about the physical structure of the database including the location of all files, the current database state etc. Each control file is associated with only one database. The control file backups are used for creating standby databases from the CommCell Console. Standby databases are used during database recovery.

The subclients need to be configured prior to running control file backups; see Enable/ Disable Control File Backups for a Specific Subclient for step-by-step instructions.

Use the following steps to backup the control file:

From the CommCell Browser, navigate to Client Computers | <Client> | Oracle | <Instance>.
Right-click the <Subclient> configured for control file backup, and click Backup.
Click Advanced.

Click the Oracle Options tab.
Select the Backup Controlfile for Standby check box.
Click OK.

Container and Pluggable database backups

Oracle 12c supports container and pluggable databases. Calypso supports the backup of container and pluggable databases. You can backup the entire container database or one or more pluggable databases.

Container databases can be backed up by creating an instance for the container database. Single and multiple pluggable databases can be separately backed up through custom RMAN scripts.

Backing up a container database

When you backup a container database, all pluggable databases that are part of the container database are also backed up.

Add an instance for the container database.
Follow the steps to create a full or incremental backup, where the instance is the one added for the container database.

Backing UP a single pluggable database

Create and customize an RMAN script file on the client computer, where the last line in the script specifies the pluggable database to back up. The line has the following format, with "pluggable_database_name" specifying the pluggable database to back up.

pluggable database pluggable_database_name;

Example: RMAN script backing up the pluggable database "SINGLE_PDB".

run {
    setlimit channel ch1 maxopenfiles 8;
    backup
    incremental level = 0
    filesperset = 32
    pluggable database SINGLE_PDB
;
}
exit;

Click here to see the RMAN log output for this example.

Execute the RMAN script.

See Running RMAN Scripts from Third Party Command Line.

Backing UP Multiple pluggable databases

Create and customize an RMAN script file on the client computer, where the last line in the script specifies the pluggable databases to back up. The line has the following format, with "pluggable_database_name1" through "pluggable_databaseN. Each database must be separated by a ",".

pluggable database pluggable_database_name1, ..pluggable_database_nameN;

Example: RMAN script backing up the pluggable databases "PLUG_DB1" and "PLUG_DB2".

run {
    setlimit channel ch1 maxopenfiles 8;
    backup
     incremental level = 0
     filesperset = 32
     pluggable database PLUG_DB1, PLUG_DB2
    ;
}
exit;

Click here to see the RMAN log output for this example.

Execute the RMAN script.

See Running RMAN Scripts from Third Party Command Line.

On Demand Backups

The content for the backup operation during On Demand backup is provided in an RMAN script and executed from the command line interface. You need to create an On Demand instance to perform on demand backup operations. Refer Creating an On Demand Instance for step by step instructions.

Create an RMAN script file on the client computer.

Example: RMAN script file for archive log backup

run { allocate channel ch1 type 'sbt_tape'

PARMS="BLKSIZE=262144";

sql 'alter system archive log current';

backup

filesperset 4

(archivelog all);

}

exit

Create the parameter file on the client with the path to the specified RMAN script file.

See RMAN Parameters for a list of mandatory and optional RMAN parameters.

Example: Parameter file argfile1.txt with path to RMAN script file, backuplogs.txt, specified:

[instancescripts]

ora11gv1,D:\backuplogs.txt

[datatype]

LOG

[sp]

SP1

[streamcount]

From the command prompt, login to the CommServe using the qlogin command.

Example: To log on to CommServe server1 with user name user1:

D:\>qlogin -cs server1 -u user1

Password:

Run the backup operation using qoperation backup.

Example: To run a full backup on client client1 using the parameter file argfile1.txt:

D:\>qoperation backup -c client1 -a Q_ORACLE -af /argfile1.txt -t Q_FULL

Supported RMAN Parameters

Parameter	Usage	Description
[instancescripts]	[instancescripts] <instance name>,<file name> Example: [instancescripts] ora11gv1,D:\backuplogs.txt	Name of the instance to be backed up, and the name of the file that contains the RMAN backup script.
[datatype]	[datatype] DATA \| LOG Example: [datatype] LOG	Mark the associated backup archive files as either DATA or LOG.
[sp]	[sp] <StoragePolicyName> Example: [sp] SP1	Name of the Storage Policy to be used for the RMAN backup job.
[streamcount]	[streamcount] <number> Example: [streamcount] 2	Number of streams to reserve for the RMAN backup job.
[rmanlogfile]	[rmanlogfile] <ouputfile location>/<outputfile name> Example: [rmanlogfile] /usr/temp1 Here, temp1 is the directory and not the file name.	This is an optional parameter. Location where the RMAN backup output file will be saved and the name of the output file. By default, an output file backup.out is created in the job results directory. You can change the name of the output file as well as the location using this parameter. In order to include the JOB ID in the output file name, you need to set the sQcmd_Bkp_RmanLogFile registry key.
[options]	QB_NO_PARTIAL_STREAM QB_NO_MULTIPLEX_STREAM QB_DO_NOT_USE_ORA_CONNECT_STRING	These are optional parameters. If specified, the backup will start only if all the specified number of streams are available. The default behavior is to reserve as many streams as possible at the start of the backup. If additional streams become available during the backup, they will be allocated dynamically. To multiplex different jobs. Do not multiplex streams of a single job If specified, the backup will use the user defined connect string and catalog connect values specified in the RMAN script instead of the values specified in the Instance Properties (Details) tab in the CommCell Console.
[mediaagent]	[mediaagent] <mediaagentname> Example: [mediaagent] MA1	This is an optional parameter. Name of the MediaAgent to be used for the backup job.
[library]	[library] <libraryname> Example: [library] LN1	This is an optional parameter. Name of the library to be used for the backup job.
[drivepool]	[drivepool] <library_name>/<drivepool_name> Example: [drivepool] LN1/DP1	This is an optional parameter. Name of the drivepool in the library to be used for the backup job.
[scratchpool]	[scratchpool] <library_name>/<scratchpool_name> Example: [scratchpool] LN1/SN1	This is an optional parameter. Name of the scratchpool in the library to be used for the backup job. The drivepool and scratchpool parameters are applicable only if a tape library is used for the RMAN backup. The drivepool and scratchpool names can be given along with the library name followed by a backslash (/) or itself alone.
[jobdescription]	[jobdescription] <jobdescription> Example: [jobdescription] weekly_data_bkp	This is an optional parameter. Job description for the backup job.

Command Line Backups

You can perform backups of one or more Oracle databases from the command line interface.

Command line backups enable you to perform backup operation on multiple clients simultaneously. In order to run the backups from command line, you need an input xml file which contains the parameters for configuring the backup options. This input xml file can be obtained from one of the following ways:

Download the input xml file template and save it on the computer from where the backup will be performed.
Generate the input xml file from the CommCell Console and save it on the computer from where the backup will be performed.

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

Perform the Backup

Download the backup_template.xml file and save it on the computer from where the command will be executed.
Execute the saved .xml script using qoperation execute command.
qoperation execute -af backup_template.xml -backupLevel FULL -subclientName xxxxx -clientName xxxxx -instanceName xxxxx

Verify the status of the job using the following command:
qlist job �j JOBID
Once the job completes, logout from the CommServe using the qlogout command.
qlogout [-cs commserver] [-all] [-tf tokenfile] [-tk token] [-h]

Examples

Performing a Full Backup	qoperation execute -af backup_template.xml -backupLevel FULL -subclientName subclient1 -clientName client1 -instanceName instance1
Performing an Incremental Backup	qoperation execute -af backup_template.xml -backupLevel INCREMENTAL -subclientName subclient1 -clientName client1 -instanceName instance1

Generate the Command Line Script from the CommCell Console

In addition to the parameters provided in the template xml file, if you want to include additional options for the backup, you can do so by selecting the required options from the CommCell Console and generate the command line xml script for the backup.

Follow the steps given below to generate a script which you can use to perform a backup from the command line interface:

From the CommCell Browser, navigate to Client Computers | <Client> | Oracle | <Instance>.
Right-click the <Subclient> and click Backup.

Select the required backup options which you want to execute using the script.
Click Save as Script.

Enter the location where you want to save the script or click Browse and navigate to the location.
The script will be saved as a .xml file and a .bat file is created.

If a file with the same name already exists in the specified location, the .xml file will be created with a timestamp. However, the .bat file will overwrite the existing file.
Enter the username and password for the user account which you want to use to perform the backup.
By default, the user account which you have used to login to CommCell console is used for performing the backup. However, if the user account does not have access to any application or database, click Use a different account.
Click OK.

Running Backups using QCommands

You can submit RMAN scripts from the Command Line Interface using QCommands. The RMAN scripts are submitted through argument files.

Available SBT Parameters

[CvClientName]

<Client_Name>

Example:

[CvClientName] 
client_name

Name of the client defined in the CommCell Console and the client name from where RMAN script runs. This parameter is optional. It is primarily used in a clustered environment.

[CvInstanceName]

<Instance_Name>

Example:

[CvInstanceName] 
instance_name

Name of the Calypso instance installed on the client from where the RMAN script runs.

This parameter is optional.

In cases of multiple instances of the software, the first installed instance would be 'Instance001'.

[CvOraSID]

<oracle_sid>

Example:

[CvOraSID] 
 DB1

Name of the Oracle System ID (SID). This parameter is used during multi stream backups and also when the Oracle database name is different from Oracle SID. It is also used for multistream restores to get single job id. This parameter is optional.

In case of a duplicate database restore, CvOraSID must be the destination SID name, otherwise in all cases it is source SID.

When you submit RMAN scripts using QCommands:

One job ID is used in the CommServe. The same Job ID is also used across different streams and attempts.
The job can be resumed from the point of failure from the CommCell Console or Command Line.
The job history can be viewed for these jobs.
A list of media can be obtained for the job in primary or secondary copy.
Job-based storage policies can be used.
Multiple streams can be allocated before the job starts.

Create an argument file on the client computer.

Example: Argument file for full backup argfile.txt

[client]

machine1_cn

[dataagent]

Q_ORACLE

[instance]

orcl

[subclient]

default

[backuptype]

Q_FULL

From the command prompt, login to the CommServe using the qlogin command.

Example: To log on to CommServe server1 with user name user1:

qlogin -cs server1 -u user1

Password:

Run the backup operation using qoperation backup.

Example: To run a full backup on client using argument file argfile.txt:

D:\>qoperation backup -af D:\argfile.txt

Running RMAN Scripts from Third Party Command Line

Backup operations can also be performed from the third-party command line using the RMAN utility. The RMAN executable is located in the ORACLE_HOME/bin directory.

Use the following steps to run backups from the third-party command line:

1.	Create an RMAN script file on the client computer.	Example: backup.txt
2.	From the RMAN command prompt on the client computer, add the environmental variables for the client and instance on which the iDataAgent is installed.	Example: allocate channel ch1 type 'sbt_tape' PARMS="ENV=(CvClientName=<client_name>, CvInstanceName=<instance_name>)"
	On Unix clients, add the SBT_LIBRARY path.	Example: allocate channel ch1 type 'sbt_tape' PARMS="SBT_LIBRARY=<software_install_path>/Base/libobk.so, ENV=(CvClientName=<client_name>, CvInstanceName=<instance_name>)" The SBT_LIBRARY path for the various platforms are listed below: AIX with 64 bit Oracle - <Client Agent Install Path>/Base64/libobk.a(shr.o) HP UX PA RISC 64 bit Oracle - <Client Agent Install Path>/Base64/libobk.sl Solaris with 64 bit Oracle -<Client Agent Install Path>/Base64/libobk.so Linux on System Z with 64 bit Oracle - <Client Agent Install Path>/Base64/libobk.so All Other Unix platforms -<Client Agent Install Path>/Base/libobk.so
3.	Add the RMAN script for backup to the file backup.txt.	Example: RMAN script file backup.txt run { allocate channel ch1 type 'sbt_tape' PARMS="BLKSIZE=262144, SBT_LIBRARY=/opt/calypso/Base/libobk.so, ENV=(CvClientName=<client_name>,CvInstanceName=<instance_name>)"; backup database; release channel ch1; }
4.	Connect to the target database.	rman target sys/sys@<databasename>
5.	Execute the RMAN script.	@backup.txt

Multi Stream Backups from Third Party Command Line

Oracle third party command line operations running on multiple streams will share the same Job ID in the Job Manager. If all the streams return failure, then the job is marked as failed. However, if one of the streams fail, it is submitted to the other stream for completion.

When you multiplex Oracle third party operations with multiple streams, each stream uses different drives by default
When performing third party command line operations, a new ClOraControlAgent.log file is generated along with ORASBT.log to record the command line jobs
When you use different storage policies for archive log backups and command line backups and if control file autobackup is configured in RMAN, when you submit a command line backup, the archive logs are backed up using log backup storage policy and control file autobackups use the command line storage policy.

Use the following steps to run multi stream backups from the third party command line:

From the RMAN command prompt, set the number of automatic channels for a specific device type.

Note that to utilize the PARALLELISM option, set the initial parameter in pfile or spfile. Eg., BACKUP_TAPE_IO_SLAVES=TRUE

In the below example, RMAN allocates two channels for the device type when using automatic channels.

CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 2 BACKUP TYPE TO BACKUPSET;

If you are using the OEM application with multiple channels, include the RMAN settings in the Oracle Enterprise Manager.

Example:

Unix:

SBT_LIBRARY=<software_install_path>

/Base64/libobk.so,

BLKSIZE=262144,ENV=(CvClientName=<client_name>,

CvInstanceName=<instance_name>,

CvOraSID=<oracle_sid>

Windows:

ENV=(CvClientName=<client_name>,

CvInstanceName=<instance_name>,

CvOraSID=<oracle_sid>),BLKSIZE=262144

Create RMAN script file to run the backup operation with a single job ID, and save it in the desired <location_path>/<file_name>. For example, D:\backup1.txt.

When creating the RMAN script, the CvClientName and CvOraSID parameters can be used optionally for backup jobs.

If you use both the RMAN PARALLELISM configure parameter and set multiple streams from RMAN script, the backup job will utilize double the number of streams. For example, if PARALLELISM is set to 2 and 2 streams are set from RMAN script, the backup job will utilize 4 streams.

Example: Content in RMAN script file backup1.txt

run

{allocate channel ch1 type 'sbt_tape'

PARMS="SBT_LIBRARY=<software_install_path>

/Base64/libobk.so,

ENV=(CvInstanceName=<instance_name>,

CvClientName=<client_name>,

CvOraSID=<oracle_sid>)";

allocate channel ch2 type 'sbt_tape'

PARMS="SBT_LIBRARY=<software_install_path>

/Base64/libobk.so,

ENV=(CvInstanceName=<instance_name>,

CvClientName=<client_name>,

CvOraSID=<oracle_sid>)";

setlimit channel ch1 maxopenfiles 1;

setlimit channel ch2 maxopenfiles 1;

backup

incremental level = 0

filesperset = 32

database include current controlfile;

sql "alter system archive log current";

backup filesperset = 1

(archivelog all delete input); }

Connect to the target database.

rman target sys/sys@<databasename>

Navigate to the saved location and execute the RMAN script.

@<file_path>backup1.txt

Previewing RMAN Scripts from CommCell Console

Prior to running a backup operation from the CommCell Console, you can preview the corresponding RMAN script for the backup job. This is useful to determine whether the selected backup options will yield the desired result in the script. You can also manually copy and save the generated RMAN script to your computer and later execute the script from the command line.

From the CommCell Browser, navigate to Client Computers | <Client> | Oracle | <Instance>.
Right-click the <Subclient> and click Backup.
Click Script Preview.
Click OK.

Customizing RMAN Scripts from CommCell Console

In addition to previewing the RMAN script, you can also modify the script from the CommCell Console. This is useful when you want to include the RMAN commands that are not supported by the software. Use the custom rman scripts to run the saved stored scripts. For example:

To run a backup stored script:

a. create stored script

[oracle@brahmani64 ~]$ rman target sys/sys@netapp catalog snap/snap@test

Recovery Manager: Release 10.2.0.4.0 - Production on Wed Oct 18 11:06:36 2011

connected to target database: NETAPP (DBID=3312111657)

connected to recovery catalog database

RMAN> create global script backup_script

2> {

3> backup database;

4> }

created global script backup_script

RMAN>

You should include recovery catalog to successfully run customized rman scripts. See Using Recovery Catalog for Backups for more information.

Use the following steps to run the custom rman scripts from CommCell Console:

From the CommCell Browser, navigate to Client Computers | <Client> | Oracle.
Right-click the <Subclient> configured for archive log backup, and then click Backup.
Click Advanced.

Click the Custom rman script tab.
Select the Customize script check box.
Edit the RMAN script as required, and then click OK.

Scheduling Backups

Follow the steps given below to schedule a backup:

1..

From the CommCell Browser, navigate to Client Computers | <Client> | Oracle.
Right-click the <Subclient> and click Backup.

Select the Backup type.
Click Schedule to schedule the backup for a specific time.
Click Configure to set the schedule for the backup job. The Schedule Details dialog displays.

Select the appropriate scheduling options. For example:

Click Weekly.
Check the days you want the run the backup job.
Change the Start Time to 9:00 PM.
Click OK to close the Schedule Details dialog.
Click OK to close the Backup Options dialog.

The backup job will execute as per the schedule.

Marking Backups with a Unique Identification Tag

You can configure tags for backups to uniquely identify a particular backup copy. These tags can be used later during restore operation to restore from a specific backup. Note that the tag defined at the backup job level will override the tag defined at the subclient level.

For a Specific Backup

From the CommCell Browser, navigate to Client Computers | <Client> | Oracle | <Instance>.
Right-click the <Subclient> and click Backup.
Click Advanced.

Click the Oracle Options tab.
In the Oracle Tag box, type the tag name.
For Example, weekly_backup.
Click OK.

For All Backups

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

Disabling Database browse during backups

By default, browse query will automatically run on the database to collect datafile names when you perform a backup. This SQL query may hang or hamper the backup performance. Use the following steps to skip database browsing before performing a backup:

From the CommCell Browser, right-click <CommServe>.
Click Properties, and then click the Registry Key Settings tab.
Click Add.
In the Name box, type sSKIPBACKUPBROWSE.
In the Location box, select CommServe.
In the Type box, select REG_SZ.
In the Value box, type Y.
Click OK.

Enhancing Backup Performance

Backup performance can be increased by setting the RMAN Disk Ratio value for distributing the backup load across disks. By default, the RMAN disk ratio is not set.

Backup performance can also be enhanced by setting additional configurations at the subclient level. See Enhancing Backup Performance for more details.

Use the following steps to set the RMAN disk ratio:

From the CommCell Browser, navigate to Client Computers | <Client> | Oracle | <Instance>.
Right-click the <Subclient> and click Backup.
Click Advanced.

Click the Oracle Options tab.
Select the Enable Rman Disk Ratio check box.
Type the number of disks in the Rman Disk Ratio box.
Click OK.

Validating Backups for Restore

You can validate previously run backups to ensure the integrity of the data for successful restores.

Use the following steps to validate the backup jobs of a subclient:

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

Disabling RMAN Warnings from RMAN Output

By default RMAN warnings are reported in the RMAN output. If such warnings are found during backups, the job is reported as �Completed With Errors�.

Use the following steps to disable the RMAN warnings:

Globally Disabling All RMAN Warnings

From the CommCell Browser, right-click <CommServe>.
Click Properties, and then click the Registry Key Settings tab.
Click Add.
In the Name box, type sIGNORERMANWARNINGS.
In the Location box, select CommServe.
In the Type box, select REG_SZ.
In the Value box, type Y.
Click OK.

Disabling All RMAN Warnings for a Specific Client

Note that if this option is set in both the client and the CommServe, the client side value will override the value set in the CommServe.

From the CommCell Browser, navigate to Client Computers.
Right-click <Client> and then click Properties.
Click the Registry Key Settings tab.
Click Add.
In the Name box, type sIGNORERMANWARNINGS.
In the Location box, select OracleAgent.
In the Type box, select REG_SZ.
On Unix Client, select Value.
In the Value box, type Y.
Click OK.

Globally Disabling Specific RMAN Warnings

From the CommCell Browser, right-click <CommServe>.
Click Properties, and then click the Registry Key Settings tab.
Click Add.
In the Name box, type sIGNORE_RMAN_WARNINGLIST.
In the Location box, select CommServe.
In the Type box, select REG_MULTI_SZ.
In the Value box, type RMAN-<number_rman_code1>,RMAN-<number_rman_code2>,...
For example, to disable RMAN-06061 warning at the CommServe level, type sIGNORE_RMAN_WARNINGLIST RMAN-06061.
Click OK.

Disabling Specific RMAN Warnings for a Client

Note that if this option is set in both the client and the CommServe, the client side value will override the value set in the CommServe.

From the CommCell Browser, navigate to Client Computers.
Right-click <Client> and then click Properties.
Click the Registry Key Settings tab.
Click Add.
In the Name box, type sIGNORE_RMAN_WARNINGLIST.
In the Location box, select OracleAgent.
In the Type box, select REG_MULTI_SZ.
On Unix Client, select Value.
In the Value box, type RMAN-<number_rman_code1>,RMAN-<number_rman_code2>,...
For example, to disable RMAN-06061 warning at the client level, type sIGNORE_RMAN_WARNINGLIST RMAN-06061.
Click OK.

Managing Jobs

Jobs can be managed in a number of ways. The following sections provide information on the different job management options available:

Restarting Jobs

Jobs that fail to complete successfully are automatically restarted based on the job restartability configuration set in the Control Panel. Keep in mind that changes made to this configuration will affect all jobs in the entire CommCell.

To Configure the job restartability for a specific job, you can modify the retry settings for the job. This will override the setting in the Control Panel. It is also possible to override the default CommServe configuration for individual jobs by configuring retry settings when initiating the job. This configuration, however, will apply only to the specific job.

Backup jobs for this Agent are resumed from the point-of-failure.

Configure Job Restartability at the CommServe Level

From the CommCell Browser, click Control Panel icon.
Select Job Management.
Click Job Restarts tab and select a Job Type.
- Select Restartable to make the job restartable.
- Change the value for Max Restarts to change the maximum number of times the Job Manager will try to restart a job.
- Change the value for Restart Interval (Mins) to change the time interval between attempts for the Job Manager to restart the job.
Click OK.

Configure Job Restartability for an Individual Job

From the CommCell Console, navigate to Client Computers | <Client> | Oracle | <Instance>.
Right-click the Subclient and select Backup.

Click Advanced.
In the Advanced Backup Options dialog box, click the Job Retry tab.
Select Enable Total Running Time and specify the maximum elapsed time before a job can be restarted or killed.
Select Kill Running Jobs When Total Running Time Expires to kill the job after reaching the maximum elapsed time.
Select Enable Number Of Retries and specify the number of retries.
Click OK.

Controlling Jobs

The following controls are available for running jobs in the Job Controller window:

Suspend	Temporarily stops a job. A suspended job is not terminated; it can be restarted at a later time.
Resume	Resumes a job and returns the status to Waiting, Pending, Queued, or Running. The status depends on the availability of resources, the state of the Operation Windows, or the Activity Control setting.
Kill	Terminates a job.

Suspending a Job

From the Job Controller of the CommCell Console, right-click the job and select Suspend.
The job status may change to Suspend Pending for a few moments while the operation completes. The job status then changes to Suspended.

Resuming a Job

From the Job Controller of the CommCell Console, right-click the job and select Resume.
As the Job Manager attempts to restart the job, the job status changes to Waiting, Pending, or Running.

Killing a Job

From the Job Controller of the CommCell Console, right-click the job and select Kill.
Click Yes when the confirmation prompt appears if you are sure you want to kill the job. The job status may change to Kill Pending for a few moments while the operation completes. Once completed, the job status will change to Killed and it will be removed from the Job Controller window after five minutes.

Additional Options

The following table describes the available additional options to further refine your backup operations:

Option

Description

Startup Options	The Startup Options are used by the Job Manager to set priority for resource allocation. This is useful to give higher priority to certain jobs. You can set the priority as follows: From the CommCell Browser, navigate to *Client Computers \| <Client> \| Oracle \| <Instance>. Right-click the Subclient* in the right pane and click Backup. Click Advanced and click Startup tab. Select the Change Priority checkbox. Enter a priority number - 0 is the highest priority and 999 is the lowest priority. Select the Start up in suspended State check box to start the job in a suspended state. Click OK.	Refer to Job Priority and Priority Precedence.
Alerts	This option enables users or user groups to get automatic notification on the status of the data protection job. Follow the steps given below to set up the criteria to raise notifications/alerts: From the CommCell Browser, navigate to *Client Computers \| <Client> \| Oracle \| <Instance>. Right-click the Subclient* in the right pane and click Backup. Click Advanced and select the Alert tab. Click Add Alert. From the Add Alert Wizard dialog box, select the required threshold and notification criteria and click Next. Select the required notification types and click Next. Select the recipients and click Next. Click Finish. Click OK.	Refer to Alerts.
Vault Tracker	This feature provides the facility to manage media that is removed from a library and stored in offsite locations. Depending on your VaultTracker setup, select the required options. Use the following steps to access and select the VaultTracker options. From the CommCell Browser, navigate to *Client Computers \| <Client> \| Oracle \| <Instance>. Right-click the Subclient* in the right pane and click Backup. Click Advanced and select the VaultTracking tab. Select the required options. Click OK.	Refer to VaultTracker or VaultTracker Enterprise.
Extended Data Retention	This option allows you to extend the expiration date of a specific job. This will override the default retention set at the corresponding storage policy copy. Follow the steps given below to extend the expiration date: From the CommCell Browser, navigate to *Client Computers \| <Client> \| Oracle \| <Instance>. Right-click the Subclient* in the right pane and click Backup. Click Advanced and select the Media tab. Select one of the following options: Infinite - Select this option to extend the expiration date by infinite number of days Number of day - Select this option to specify the number of days to extend the expiration date and then enter the number of days. Click OK.	Refer to Extended Retention Rules.
Allow Other Schedules to Use Media Set	The Allow Other Schedules to use Media Set option allows jobs that are part of the schedule or schedule policy and using the specific storage policy to start a new media. It also prevents other jobs from writing to the same set of media. From the CommCell Browser, navigate to *Client Computers \| <Client> \| Oracle \| <Instance>. Right-click the Subclient* in the right pane and click Backup. Click Advanced and select the Media tab. Select the Allow Other Schedules To Use Media Set check box. Click OK.	Refer to Creating an Exportable Media Set.
Mark Media Full	This option marks the media as full, two minutes after the successful completion of the data protection job. This option prevents another job from writing to this media. Follow the steps given below: From the CommCell Browser, navigate to *Client Computers \| <Client> \| Oracle \| <Instance>. Right-click the Subclient* in the right pane and click Backup. Click Advanced and select Media tab. Select the Mark Media Full on Success check box. Click OK.	Refer to Start New Media.
Start New Media	The Start New Media option enables you to start the data protection operation on a new media. This feature provides control over where the data physically resides. Use the following steps to start the data protection operation on a new media: From the CommCell Browser, navigate to *Client Computers \| <Client> \| Oracle \| <Instance>. Right-click the Subclient* in the right pane and click Backup. Click Advanced and select the Media tab. Select the Start New Media check box. Click OK.	Refer to Start New Media.
Data Path Options	Data Protection operations use a default Library, MediaAgent, Drive Pool, and Drive as the Data Path. You can use this option to change the data path if the default data path is not available. Follow the steps given below to change the default data path: From the CommCell Browser, navigate to *Client Computers \| <Client> \| Oracle \| <Instance>. Right-click the Subclient* in the right pane and click Backup. Click Advanced and select the Data Path tab. Select the MediaAgent and Library. Select the Drive Pool and Drive for optical and tape libraries. Click OK.	Refer Change Data Path.
CommCell Readiness Report	The CommCell Readiness Report provides you with vital information, such as connectivity and readiness of the Client, MediaAgent and CommServe. It is useful to run this report before performing the data protection or recovery job. Follow the steps given below to generate the report: From the Tools menu in the CommCell Console, click Reports. Navigate to Reports \| CommServe \| CommCell Readiness. Click the Client tab and click the Modify button. In the Select Computers dialog box, clear the Include All Client Computers and All Client Groups check box. Select the client from the Exclude list. Click the Include > button. Click OK. Click the MediaAgent tab. Clear the Include All MediaAgents checkbox. Select the MediaAgent from the Exclude list. Click Include >. Click Run. The generated report is displayed.	Refer to CommCell Readiness Report.
Backup Job Summary Report	The Backup Job Summary Report provides you with information about all the backup jobs that are run in last 24 hrs for a specific subclient. You can get information such as status, time, data size etc. for each backup job. It is useful to run this report after performing the backup. Follow the steps given below to generate the report: From the Tools menu in the CommCell Console, click Reports. Navigate to Reports \| Jobs \| Job Summary. Click Data Management on the General tab in the right pane. Select the Computers tab. Click Subclient and select the Edit tab. Navigate to Client Computers \| <Client> \| File System \| Backup Set \| Subclient. Click Run.	Refer to Backup Job Summary Report.

Advanced Backup - Oracle iDataAgent

Table of Contents

Container and Pluggable database backups

Backing up a container database

Backing UP a single pluggable database

Backing UP Multiple pluggable databases

Examples

Available SBT Parameters

Configure Job Restartability at the CommServe Level

Configure Job Restartability for an Individual Job

Suspend

Resume

Kill

Suspending a Job

Resuming a Job

Killing a Job