Table of Contents |
Related Topics |
Cumulative Incremental Backups Logs Not Backed Up a Specified Number of Times Deleting Archive Logs for a Specific Backup Running Backups using QCommands Running RMAN Scripts from Third Party Command Line Multi Stream Backups from Third Party Command Line Previewing RMAN Scripts from CommCell Console Customizing RMAN Scripts from CommCell Console Marking Backups with a Unique Identification Tag |
Provides comprehensive information on scheduling jobs. Provides comprehensive information on managing jobs. Provides comprehensive information on running jobs from the command line. |
Full backups provide the most comprehensive protection of data.
Backups for any client start with a full backup. If the database is in NOARCHIVELOG mode, you should perform offline backup only.
You can perform a full backup of an online or offline database.
Use the following steps to run a full backup:
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. |
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:
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:
Use the following steps to backup all archive logs. Note that this is the default option:
Use the following steps to backup archive logs older than a specified number of days.
Use the following steps to backup archive logs not older than a specified number of days.
Use the following steps to backup archive logs between a specified time:
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:
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:
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.
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.
Use the following steps to backup archive logs that have failed to backup a specified number of times earlier:
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.
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:
You can submit RMAN scripts from the Command Line Interface using QCommands. The RMAN scripts are submitted through argument files.
When you submit RMAN scripts using QCommands:
1. | Create an argument file on the RAC client. | Example: Argument file for full backup argfile.txt [client] machine1_cn [dataagent] Q_ORACLE [instance] orcl [subclient] default [backuptype] Q_FULL |
2. | 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: |
3. | Run the backup operation using qoperation backup. | Example: To run a full backup on RAC client client1
using the parameter file argfile1.txt: D:\>qoperation backup -af D:\argfile.txt |
Parameter Name | Description | Example |
[CvClientName]
|
Name of the client defined in the CommCell Console. This parameter is optional. It is primarily used in a clustered environment. |
[CvClientName] client_name |
[CvInstanceName] |
Name of the Calypso instance installed. This parameter is optional. In cases of multiple instances of the software, the first installed instance would be 'Instance001'. |
[CvInstanceName] Instance001 |
[CvOraSID] | Name of the Oracle System ID (SID). This parameter is used during multi stream backups and also when the Oracle instance name is different from Oracle SID. |
[CVOraSID] DB1 |
[-hn] | RAC control host name for the backup/restore job. |
[-hn] dbserve10.mycompany.com |
[CVOraRacDBName] | Oracle RAC database name for the backup/restore job. |
[CVOraRacDBName] asmdb |
[CvOraRacDBClientName] | Oracle RAC database client name for cross machine and/or duplicate database restore job. If you are restoring the database to a computer that is not part of the RAC pseudo client (cross machine restore), you need to define the environmental variable CVOraRacDBClientName to specify a client that is part of the RAC pseudo client. |
[CvOraRacDBClientName] dbserve99 |
Use the following steps to run backups from the third-party command line:
1. | Create an RMAN script file on the RAC client. | Example: RMAN script file backup.txt |
2. | From the RMAN command prompt on the RAC client, add the environmental variables for the RAC client and instance on which the iDataAgent is installed. | Example: allocate channel ch1 type 'sbt_tape' PARMS="ENV=(CvClientName=<client_name>, CVOraRacDBName=<rac_database_name>, CvInstanceName=<instance_name>, -hn=<hostname>)" |
On RAC clients for Unix, add the SBT_LIBRARY path. | Example:
allocate channel ch1 type 'sbt_tape' connect <sql_connect_string> PARMS="SBT_LIBRARY=<software_install_path>/Base/libobk.so, ENV=(CvClientName=<client_name>, CvInstanceName=<instance_name>, CVOraRacDBName=<rac_database_name>)"
The SBT_LIBRARY path for the various platforms are listed below:
|
|
3. | Add the RMAN script for backup to the file backup.txt on the RAC client. | 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>, CVOraRacDBName=<rac_database_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 |
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.
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.
Use the following steps to run multi stream backups from the third party command line:
1. | From the RMAN command prompt on the RAC client, 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; |
2. | 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=<rac_client_name>, CVOraRacDBName=<rac_database_name>, CvInstanceName=<instance_name>, -hn=<host_name>)
Windows: ENV=(CvClientName=< CvClientName=<rac_client_name>, CVOraRacDBName=<rac_database_name>, CvInstanceName=<instance_name>, -hn=<host_name>, BLKSIZE=262144) |
3. | 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. RMAN script to run backup using two channels for node 1 and two channels for node 2. run {allocate channel ch1 type 'sbt_tape' PARMS="SBT_LIBRARY=<software_install_path> /Base/libobk.so,BLKSIZE=262144, ENV=(CvClientName=<rac_client_name1>, CVOraRacDBName=<rac_database_name>, CvInstanceName=<instance_name>, -hn=<host_name>)";
allocate channel ch2 type 'sbt_tape' PARMS="SBT_LIBRARY=<software_install_path> /Base/libobk.so,BLKSIZE=262144, ENV=(CvClientName=<rac_client_name1>, CVOraRacDBName=<rac_database_name>, CvInstanceName=<instance_name>, -hn=<host_name>)";
allocate channel ch3 type 'sbt_tape' connect <connect_string> PARMS="SBT_LIBRARY=<software_install_path> /Base/libobk.so,BLKSIZE=262144, ENV=(CvClientName=<rac_client_name2>, CVOraRacDBName=<rac_database_name>, CvInstanceName=<instance_name>, -hn=<host_name>)";
allocate channel ch4 type 'sbt_tape' connect <connect_string> PARMS="SBT_LIBRARY=<software_install_path> /Base/libobk.so,BLKSIZE=262144, ENV=(CvClientName=<rac_client_name2>, CVOraRacDBName=<rac_database_name>, CvInstanceName=<instance_name>, -hn=<host_name>)";
setlimit channel ch1 maxopenfiles 8; setlimit channel ch2 maxopenfiles 8; backup incremental level = 0 filesperset = 8 database include current controlfile; } |
Example: rman target sys/sys@racdb5 << EOF run { allocate channel ch1 type 'sbt_tape'PARMS= "SBT_LIBRARY=/oracle/calypso/Base/libobk.so,BLKSIZE=262144,ENV=(CvClientName=rac1,CVOraRacDBName=racdb,CvInstanceName=Instance001,-hn=rac1.devemc.Bull Calypso.com)";
allocate channel ch2 type 'sbt_tape'PARMS="SBT_LIBRARY=/oracle/calypso/Base/libobk.so,BLKSIZE=262144,ENV=
allocate channel ch3 type 'sbt_tape' connect sys/sys@racdb6PARMS="SBT_LIBRARY=/oracle/calypso/Base/libobk.so,BLKSIZE=262144,ENV=
allocate channel ch4 type 'sbt_tape' connect sys/sys@racdb6PARMS="SBT_LIBRARY=/oracle/calypso/Base/libobk.so,BLKSIZE=262144,ENV= setlimit channel ch1 maxopenfiles 8; setlimit channel ch2 maxopenfiles 8; backup incremental level = 0 filesperset = 8 database include current controlfile; } EOF |
4. | Connect to the target database. | rman target sys/sys@<databasename> |
5. | Navigate to the saved location and execute the RMAN script. | @<file_path>backup1.txt |
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.
|
![]() |
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.
Follow the steps given below to schedule a backup:
1.. |
|
![]() |
For example, consider data files distributed across 10 disks that supply data at 10 bytes/second and a tape drive that needs 40 bytes/second to keep streaming. In this case, you can set the disk ratio value to 4, which will direct RMAN to include data files from 4 disks in each backup 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:Use the following steps to validate the backup jobs of a subclient:
Jobs can be managed in a number of ways. The following sections provide information on the different job management options available:
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. |
|
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. |
The following table describes the available additional options to further refine your backup operations:
Option | Description | Related topics |
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:
|
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:
|
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.
|
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:
|
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.
|
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:
|
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:
|
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:
|
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:
|
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:
|
Refer to Backup Job Summary Report. |