SnapProtect - Advanced Backup - SAP Oracle iDataAgent

Table of Contents

Choosing the Backup Interface

When defining subclients for various SnapProtect backup operations, you can select different SAP interfaces as mentioned below:

Util_File

The util_file interface is used when you need to perform a full backup or a selective online full backup operation. When selecting this option for online backup, the Oracle database is locked till the full backup operation is completed.

  1. From the CommCell Browser, right-click the Subclient and click Properties.
  2. Click Content tab.
  3. Select util_file to perform a full backup of SAP for Oracle data.
  4. Click OK to save your settings.

Util_Vol

When you perform backups using the util_vol backup interface, the entire database is locked till the backup operation is completed.

Use the following steps to configure backups using util_vol backup interface:

  1. From the CommCell Browser, navigate to <Client> | SAP for Oracle | <Instance>
  2. Right-click the Subclient and click Properties.
  3. Click Content tab.
  4. Select util_vol to perform a backup operation.
  5. Click OK to save your settings.

Util_Vol_Online

The util_vol_online backups are similar to the util_vol backups. However, when using these type of backups, each volume that is being backed up is locked during the backup and is released once the backup is completed.

Use the following steps to configure backups using util_vol_online backup interface:

  1. From the CommCell Browser, navigate to <Client> | SAP for Oracle | <Instance>
  2. Right-click the Subclient and click Properties.
  3. Click Content tab.
  4. Select util_vol_online to perform a backup operation.
  5. Click OK to save your settings.

Full Backup

A full backup contains all the data that comprises a subclient's contents. Though, full backups provide the most comprehensive protection of data, it consumes most amount of time and resources.

  1. From the CommCell Console, navigate to <Client> | SAP for Oracle |<Instance>
  2. Right-click the Subclient and click Backup.
  3. Select Full as backup type and Immediate to run the job immediately.
  4. Click OK.
  5. You can track the progress of the job from the Job Controller window of the CommCell console.
  6. Once job is complete, view the details of job from the Job History.
  7. Right-click the client computer, click View and then click View Job History.
  8. Click OK.
  9. You can view the following details about the job by right-clicking the job:
    • Items that failed during the job
    • Items that succeeded during the job
    • Details of the job
    • Events of the job
    • Log files of the job
    • Media associated with the job

If you are using a stand-alone drive, you are  prompted to load a specific cartridge into the drive. If you are using a library, you will not receive this prompt. The system loads the tapes automatically. Your cartridges should be appropriately labeled. This will enable you to locate the correct cartridge for a restore job, if necessary.

Offline Backups

Note: When you perform an offline backup from the CommCell Console, the database is shut down by default. You can disable the forced shut down by setting the sNOOFFLINEFORCE Additional Setting to Y.

Online Backups

Online backups are performed when the database is online and in ARCHIVELOG mode. Online backups include the data files and archived log files. You can perform a full or incremental backups when the database is online. These backups do not require database downtime and are extremely useful when you need to perform a point-in-time restore of the Oracle database.

In order to backup the Oracle database when it is online, you can create a separate user-defined subclient for online backup. For information on creating subclients, see Creating Subclient for online Backups.

Backing Up Individual Datafiles and Tablespaces

Create a separate subclient to back up a subset of the online database that frequently changes. For information on creating subclients, see Creating Subclient to Backup Individual Datafiles/Tablespaces.

Archive Log Backups

Use log backups in the following scenarios.

  • To restore the database to the most recent state after a database failure.
  • To restore specific logs, which are identified using a serial number or identification tag that are missing in the database.
  • To restore logs from a specific time range that were lost due to a hard disk corruption, use a point-in-time archive log restore.

The current redo log file is closed (even if it is not filled up completely) and the next redo log file is used for writing using a log switch during an archive log backup. The closed redo log file is then archived during the log phase.

To back up only the archive logs, create a separate subclient for archive logs.  For information on creating subclients, see Creating Subclient for Log Backups.

By default, the first backup operation on the default subclient includes the entire database (data and archive logs) when the database is online and in ARCHIVELOG mode.

If archive log destination is different than the default $SAPDATA_HOME/saparch location, set the <SID>_sSAPARCH Additional Setting to enable the CommCell Console backup to obtain the new SAPARCH location.

While running an SnapProtect backup, select the Use Traditional Backup for Logs check box to traditionally back up the logs after snap backup of data is complete. You can use this option if you do not want to run snap backup of logs. The Job Controller first displays a snap backup job for data. Once this job completes, an incremental log backup job starts automatically.

  • Selective Online Full check box gets disabled under the Content tab if you decide to back up the logs traditionally.
  • If you backup the data after selecting the Use Traditional Backup for Logs check box and then try to restore it by selecting the copy precedence as 1, the restore job will fail. For more information, see KB article SAPOR0001.

Optimizing SnapProtect Backup

Each SnapProtect backup job snaps many volumes that are used for data, archive logs, detail and summary files, database init files etc. A large number of SnapProtect backup jobs can quickly consume the snap data reserve. To overcome this, use the CV_SAP_SNAP_BKP_OPTIMIZE additional setting to reduce the total number of snapshots per job.

The following table shows the snapshots of volumes with this additional setting for Online backups. The following paths are assumed to be the default locations:

Snapshots of volumes without the setting Snapshots of volumes with the setting
Data detail and summary files location - $SAPDATA_HOME<SID>\sapbackup Data detail and summary files location - $SAPDATA_HOME<SID>\sapbackup
DATA directory - $SAPDATA_HOME<SID>\sapdata DATA directory - $SAPDATA_HOME<SID>\sapdata
Log detail and summary files location - $SAPDATA_HOME<SID>\saparch Log detail and summary files location - $SAPDATA_HOME<SID>\saparch
Logs directory - $SAPDATA_HOME<SID>\saparch Logs directory - $SAPDATA_HOME<SID>\saparch
Database Init files - $SAPDATA_HOMEdbs NOT SNAPPED
Space reorg file - $SAPDATA_HOME<SID>\sapreorg NOT SNAPPED
Ctrl file -  $SAPDATA_HOME<SID>\sapbackup Ctrl file -  $SAPDATA_HOME<SID>\sapbackup

The following table shows the snapshots of volumes with this additional setting for Offline backups.

Snapshots of volumes without the setting Snapshots of volumes with the setting
Data detail and summary files location - $SAPDATA_HOME<SID>\sapbackup Data detail and summary files location - $SAPDATA_HOME<SID>\sapbackup
DATA directory - $SAPDATA_HOME<SID>\sapdata DATA directory - $SAPDATA_HOME<SID>\sapdata
Log detail and summary files location - $SAPDATA_HOME<SID>\saparch Log detail and summary files location - $SAPDATA_HOME<SID>\saparch
Logs Directory - $SAPDATA_HOME<SID>\saparch Logs Directory - $SAPDATA_HOME<SID>\saparch
Redo logs directory -  $SAPDATA_HOME<SID>\origlog*  $SAPDATA_HOME<SID>\mirrlog* Redo logs directory -  $SAPDATA_HOME<SID>\origlog*  $SAPDATA_HOME<SID>\mirrlog*
Database Init files - $SAPDATA_HOMEdbs NOT SNAPPED
Space reorg file - $SAPDATA_HOME<SID>\sapreorg NOT SNAPPED
Ctrl file -  $SAPDATA_HOME<SID>\sapbackup Ctrl file -  $SAPDATA_HOME<SID>\sapbackup

Follow these steps to enable snapshot optimization.

  1. From the CommCell Browser, navigate to Client Computers |<Client>.
  2. Right-click <Client>, and then click Properties. On the Client Properties dialog box, click Advanced.
    1. On the Additional Settings tab of the Advanced Client Properties dialog box click Add.
    2. On the Add Additional Settings dialog box:
      • In the Name field, type CV_SAP_SNAP_BKP_OPTIMIZE.
      • The Category and Type are automatically filled in.
      • In the Value field, type Y.
      • Click OK to close the Add Additional Settings dialog box
    3. Click OK to close the Advanced Client Properties dialog box.
  3. Click OK to close the Client Properties dialog box.

Selective Online Full Backup

You can use the selective copy of a full backup to make copies of the backup using an auxiliary copy operation. The selective copy advantages include:
  • The data and log backups use the same storage policy and reside on the same media.
  • The data and log backups use the same selective online full backup data aging rules. For more information on selective copies, see Secondary Copy (Selective Copy).

Selective online full backup jobs include complete and up-to-date data because of the following built-in job management features.

  • Currently running SAP for Oracle backup jobs must complete before the selective online full backup job begins.
  • During the data backup phase of a selective online full backup job, the only other Oracle data backup jobs that are allowed to run on the same instance are archive log backups. The log backup jobs are forced to use the selective online full backup storage policy. To override this option and use a separate log storage policy for log backups run during the selective online backup, see Configuring the Storage Policy for a Log Backup During a Selective Online Full Backup.
  • During the log backup phase of a selective online full backup, no other Oracle data or log backup jobs can run on the same instance. New jobs started on the instance are queued in the Job Controller until the selective online full backup job is completed.
  • If a selective online full backup is restarted during a currently running selective online full backup, the current job restarts from the beginning of the phase. For example, if a selective online full backup job goes to the pending state during the data phase, when restarted, the job starts from the beginning of the data phase.

For information on special data aging rules for selective online full backups, see Selective Online Full Backup Retention Rules.

Before You Begin

Procedure

Expand All

UTIL_FILE

  1. Include the SelectiveOnlineFull parameter in the $ORACLE_HOME/dbs/init<SID>.utl file and set the parameter value to 1.

    Example

    SAPOracle11gr2124@saporavm2>vi initCER.utl
    numstreams
    1
    SelectiveOnlineFull
    1

  2. On the command line, type the following command to run the data backup.

    brbackup -t online -d util_file -m all -c force -u /

  3. On the command line, type the following command to run the log backup.

    brarchive –d util_file –s –c force u /

RMAN_UTIL

  1. Include the SelectiveOnlineFull parameter in the $ORACLE_HOME/dbs/init<SID>.sap file and set the parameter value to 1.

    Example

    RMAN_PARMS="SBT_LIBRARY= /Base/libobk.so,BLKSIZE=1048576,ENV=(CvClientName= ,CvInstanceName= ,SelectiveOnlineFull=1)

  2. On the command line, type the following command to run the data backup.

    brbackup -t online -d rman_util -m FULL -c force -u /

  3. On the command line, type the following command to run the log backup.

    brbackup -t online -d rman_util -s -c force

Third Party Command Line Backups

In addition to using the CommCell Console, you can also perform full and incremental backups from the Command Line Interface. However, ensure that the SnapProtect check box is selected in the CommCell Console, both at the client level and the instance level. For step-by-step instructions, see SnapProtect - Getting Started - Configuration.

You can perform Command Line backup operations using one of the following methods:

Using SAP Command Line

Perform backups from the SAP command line, by using the BRBACKUP  and BRARCHIVE command. The database can be online or offline for the backup.

The syntax is:

brbackup -t [offline|online] -d [util_file|rman_util|util_file_online] -m [full|incr]

For information on the BRBACKUP, and BRARCHIVE command options, go to the SAP Help website, Command Options for BRBACKUP.

You can use the BRBACKUP command to backup the following data with the database online, or offline.

  • The database,
  • Control Files
  • Datafiles within tablespaces
  • Log file

The BRBACKUP command saves profiles and logs that are relevant to the backup.

You can use the BRARCHIVE command to back up archived redo logs.

Expand All

BRBACKUP Examples

  • Perform a full backup using the util_file interface

    brbackup -t online -d util_file -m all -u /

  • Perform a full backup using rman_util interface

    brbackup -t online -d rman_util -m FULL -u /

  • Perform an incremental backups using rman_util interface

    brbackup -t online -d rman_util -m INCR -u /

BRARCHIVE Examples

The BRARCHIVE command is used to backup the archived redo log files.

  • Perform a log backup using the util_file interface

    brarchive -sd -b -m all -d util_file -c

  • Perform a log backup using rman_util interface

    brarchive -d rman_util -s

  • To archive the offline redo logs

    brarchive -d util_file -s

  • To create a second copy of the offline redo log files which were already archived

    brarchive -d util_file -sc

  • To archive the offline redo logs to two backup devices (tape devices) in parallel

    brarchive -d util_file -ss

  • To archive offline redo log files and then delete these files

    brarchive -d util_file -sd

  • To create a second copy of the offline redo log files that have already been archived and then delete these files

    brarchive -d util_file -scd

  • To archive the offline redo logs to two backup devices (tape devices) in parallel and then delete the files

    brarchive -d util_file -ssd

  • To create a second copy of offline redo log files that have already been archived and then archive the newly created offline redo log files

    brarchive -d util_file -cs

  • To create a second copy of offline redo log files which were already archived. These are then deleted and archiving of the newly created offline redo log files is begun

    brarchive -d util_file -cds

  • To delete offline redo log files that have been archived once

    brarchive -d util_file -ds

  • To delete offline redo log files that have been copied twice

    brarchive -d util_file -dc

Parameter File

Before you run backups from the SAP command line, ensure that the appropriate parameter file containing information regarding the instance and the client is in place. Be sure to include at least the CVInstanceName parameter name followed by the name of the instance and also the CVClientName parameter name followed by the name of the client.

  • For SAP Oracle on Unix include this information in the init<SID>.utl file under the $ORACLE_HOME/dbs directory.

  • For SAP Oracle on Windows, include this information in the init<SID>.utl file in any location and execute the BRBACKUP command with option –r .

For any software version, if your backups are using the SAP utility files, be sure to modify the init<SID>.utl file

For details on the parameters, see Supported SAP Oracle Util File Parameters.

When performing backups from the command line, note that the multi-stream log backups are supported only from the command line interface.

For comprehensive information on multi streaming, refer to the Streams documentation.

Consistent Online Backups

In a consistent online backup, the database files and the offline redo log files are backed up together in the same backup volume. This backup type allows you to take logical consistent backups without having to shutdown the database.

The offline redo log files backed up along with the database are completely independent from the BRARCHIVE log backups.

Use the following steps to run a consistent online full backup:

  1. Include the instance name and client name parameters in the init.utl file.

    For example:

    CvInstanceName
    Instance001
    CvClientName
    client1

  2. From the SAP command line, type the command to run a consistent online full backup.

    brbackup -t online_cons -d util_file -m full

BR*Tools Interface

In addition to SAP command line, you can also use the BR*Tools user interface to perform backup and restore operations. BR*Tools is an easy-to-use interface that provides menus to run different types of backup or restore operations. For detailed information on using the BR*Tools interface, see SAP documentation.

Prior to performing backup operations using BR*Tools interface, ensure to set the appropriate values in the parameter file.

A sample BR*Tools backup operation is given below:

  1. From the BR*Tools interface main menu, select 4 to perform a backup operation.

    BR*Tools main menu\par
    \par
    1 = Instance management\par
    2 - Space management\par
    3 - Segment management\par
    4 - Backup and database copy\par
    5 - Restore and recovery\par
    6 - Check and verification\par
    7 - Database statistics\par
    8 - Additional functions\par
    9 - Exit program\par
    \par
    Standard keys: c - cont, b - back, s - stop, r - refr, h - help\par
    -----------------------------------------------------------\par
    BR0662I Enter your choice:\par

  2. From the BR*Tools choice menu, select 1 to perform a database backup.

    BR0656I Choice menu 9 - please make a selection\par
    -------------------------------------------------------------------------------\par
    Backup and database copy\par
    \par
    1 = Database backup\par
    2 - Archivelog backup\par
    3 - Database copy\par
    4 - Non-database backup\par
    5 - Backup of database disk backup\par
    6 - Verification of database backup\par
    7 - Verification of archivelog backup\par
    8 - Additional functions\par
    9 - Reset program status\par
    \par
    Standard keys: c - cont, b - back, s - stop, r - refr, h - help\par
    -----------------------------------------------------------\par
    \b BR0662I Enter your choice:\b0\par

  3. From the BR*Tools input menu, select the input values, such as device type, backup type etc.

    For example, select 2 to specify the device type.

    BR0657I Input menu 15 - please check/enter input values\par
    -------------------------------------------------------------------------------\par
    BRBACKUP main options for backup and database copy\par
    \par
    1 - BRBACKUP profile (profile) ....... [initCER.sap]\par
    2 - Backup device type (device) ...... [util_file]\par
    3 # Tape volumes for backup (volume) . []\par
    4 ~ BACKINT/Mount profile (parfile) .. [?/dbs/init@.utl]\par
    5 - Database user/password (user) .... [/]\par
    6 - Backup type (type) ............... [offline_force]\par
    7 - Disk backup for backup (backup) .. [no]\par
    8 # Delete disk backup (delete) ...... [no]\par
    9 ~ Files for backup (mode) .......... [all]\par
    \par
    Standard keys: c - cont, b - back, s - stop, r - refr, h - help\par
    ---------------------------------------------------------\par
    BR0662I Enter your choice:\par

  4. Specify the value for the device type.

    For example, util_file

    BR0280I BRTOOLS time stamp: 2010-02-23 17.58.47\par
    BR0681I Enter string value for "device" (tape|tape_auto|tape_box|pipe|pipe_auto|pipe_box|disk|stage|
    util_file|util_file_online|rman_util|rman_disk|rman_stage) [util_file]:\par

  5. From the BRBackup main options menu, select 4 to provide the parameter file.

    BRBACKUP main options for backup and database copy\par
    \par
    1 - BRBACKUP profile (profile) ....... [initCER.sap]\par
    2 - Backup device type (device) ...... [util_file]\par
    3 # Tape volumes for backup (volume) . []\par
    4 ~ BACKINT/Mount profile (parfile) .. [?/dbs/init@.utl]\par
    5 - Database user/password (user) .... [/]\par
    6 - Backup type (type) ............... [offline_force]\par
    7 - Disk backup for backup (backup) .. [no]\par
    8 # Delete disk backup (delete) ...... [no]\par
    9 ~ Files for backup (mode) .......... [all]\par
    \par

  6. Enter the path to the parameter file.

    Example;

    /dbs/initCER.utl

    BR0280I BRTOOLS time stamp: 2010-02-23 17.59.26\par
    BR0681I Enter string value for "parfile" [?/dbs/init@.utl]:\par

  7. Go to step 5. Select the backup options as required.

    Repeat this process, till you have entered all the required parameters for the backup operation.

    Once all the options are selected, enter c to initiate the backup operation.

  8. The summary of the options selected, will be displayed.

    Enter c to continue the operation.

    BR0291I BRBACKUP will be started with options '-p initCER.sap -d util_file -r ?/dbs/initCER.utl -t online -m all -k no -l E'\par
    \par
    BR0280I BRTOOLS time stamp: 2010-02-23 18.03.38\par
    BR0670I Enter 'c[ont]' to continue, 'b[ack]' to go back, 's[top]' to abort:\par

BACKINT Interface

Before You Begin

  • Edit the init<SID>.utl file and add:

    CvInstanceName
    Instance001
    CvClientName
    client1

About This Task

BACKINT  uses the SAP BRTools to communicate with the SAP Oracle Database and perform backup and restore operations. You can iinquire about backup requests and executes them.

backint -u <user_id> [-f <function>] [-t <type>] [-p <par_file>] [-i <in_file>] [-o <out_file>] [-c]

Option Description
-u The BACKINT user ID. This will be the database instance name (ORACLE_SID)
-f The operation (backup, restore, or inquire). The default is backup.
-t The backup type: file or file_online. The default is file.
-p The backup utility parameter file containing the parameters that determine the backup procedure specific to the backup utility. SAP BRtools specifies the location of this utility parameter file in the parameter file (parameter util_par_file), but does not evaluate its contents.
-i The input file (text file) that defines the files and directories to be backed up. The default is standard input.
-o The output text file that will contain the processing messages and the results of the operation. The default is the standard output.
-c The mode: attended or unattended mode (does not involve user interaction). The default is attended.

Procedure

Backup Example

Use the following example, substituting the SID, input_text_fil and output_file variables.

backint -u SID -f backup -t file –p /oracle/SID/dbs/initSID.utl -i input_text_file -o output_file

Expand All

Output

Program: backint
Parameters: Client node: RC1
Function: backup
Input File: input_text_file
Output File: output_file
Profile: /oracle/SID/dbs/initC11.utl
Parallel sessions: 1 BKI0008I: Number of bytes to save: 0.012 MB.
Backup started ... #SAVED SAP___9409020458 /oracle/SID/sapdata1/user1i_1/user1i.data1
BKI0022I: Bytes saved so far: 0.012 MB (100.0%).

Inquire a Backup Request

To get a list of all the backup jobs that contain a specified file name, use a # in front of the file name.

#NULL /oracle/SID/sapdata1/user1i_1/user1i.data1

Example

Use the following example, substituting the SID, input_text_fil and output_file variables.

Program: backint
Parameters: Client node:
RC1 Function: backup
Input File: input_text_file
Output File: output_file
Profile: /oracle/CER/dbs/initCER.utl
Parallel sessions: 1
#BACKUP SAP___9409020458 /oracle/SID/sapdata1/user1i_1/user1i.data1
#BACKUP SAP___9409020450 /oracle/SID/sapdata1/user1i_1/user1i.data1

Scheduling a Backup

  1. From the CommCell Console, navigate to the Client Computers | <Client> | SAP for Oracle | <Instance>
  2. Right-click the Subclient, and then click Backup.

  3. 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.

  4. 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.

Managing Jobs

Once you initiate the backup operation, a backup job is generated in the Job Controller. 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.

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 that 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

  1. From the CommCell Console ribbon, click the Home tab, and then click Control Panel.
  2. Under System, click Job Management.

    The Job Management dialog box appears.

  3. Click Job Restarts tab.
  4. From the Job Type list, select the appropriate item.
  5. Select the Restartable check box to make the job restartable.
  6. In the Max Restarts box, change the maximum number of times the Job Manager will try to restart a job.
  7. In the Restart Interval (Mins) box, change the time interval between attempts for the Job Manager to restart the job.
  8. Click OK.

Configure Job Restartability for an Individual Job

  1. From the CommCell Console, navigate to <Client> | SAP for Oracle | <Instance>
  2. Right-click the Subclient and select Backup.
  1. Click Advanced.
  2. In the Advanced Backup Options dialog box, click the Job Retry tab.
  3. 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.

  4. Select Enable Number Of Retries and specify the number of retries.
  5. 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

  1. From the Job Controller of the CommCell Console, right-click the job and select Suspend.
  2. 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

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

Killing a Job

  1. From the Job Controller of the CommCell Console, right-click the job and select Kill.
  2. 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.

Job Status

BR*Tools Error Code Description Job Status
0 Successful Completed
1 Warnings – all files were processed (for example, backed up or restored) Completed With Warning
2 Canceled during the initialization phase by a user or other signal Completed With One or More Errors
3 Errors occurred during the initialization phase, processing was not started Completed With One or More Errors
4 Canceled by a user or other signal during processing Completed With One or More Errors
5 Started, but not completed because errors occurred during processing Completed With One or More Errors
6 Internal termination Completed With One or More Errors
9 Successful, but did not finish. Details can be seen in the summary logs that are copied to the backup media Completed With One or More Errors

Additional Options

Several additional options are available to further refine your backup operations. The following table describes these options, as well as the steps for configuring them.
Be sure to read the overview material referenced for each feature prior to using them.

Option Description Related Topics
Data You can select transaction logging options for a backup job.
  1. From the CommCell Browser, click Client Computers | SAP For Oracle | < instance name >.The default and other subclients (if available) are displayed on the right-hand window pane.
  2. Right-click the subclient.
  3. Click Backup.
  4. Click Advanced.
  5. Click  Data.
  6. Select the desired Catalog option for transaction logging.
  7. Click OK.
 
Startup Options The Startup options facilitate the startup behavior of the backup job.
  1. From the CommCell Browser ,Click Client Computers |SAP for Oracle | <instance name> |.

    The default and other subclients (if available) are displayed on the right-hand windowpane).

  2. Right-click the subclient,
  3. Click Backup.
  4. Click Advanced.
  5. Click Startup.
    • Select Use Default Priority option to use default priority for the job.
    • Select Change priority option to change the priority for a job, between 0 (highest priority) and 999 (lowest priority).
  6. Select Start up in Suspended State option to add a level of manual control.
  7. Click OK.
Refer to Job Priority and Priority Precedence for more information.
Job Retry Options Job Retry options enable you to configure the retry behavior of the backup jobs.
  1. From the CommCell Browser, click Client Computers | SAP For Oracle | < instance name >. The default and other subclients (if available) are displayed on the right-hand window pane.
  2. Right-click the subclient.
  3. Click Backup.
  4. Click Advanced.
  5. Click Job Retry Options.
  6. Select Enable Total Running Time.
  7. Select Enable Number of Retries option to select number of times the Job Manager will attempt to restart the job.
  8. Select Kill Running Jobs When Total Running Time Expires option to kill the job when the specified Total Running Time has elapsed.
  9. Click OK.
Refer to the Job Management documentation for a comprehensive overview prior to using these features
Media Options You can start the backup operation in a new media.
  1. From the CommCell Browser, click Client Computers | SAP For Oracle | < instance name >. The default and other subclients (if available) are displayed on the right-hand window pane.
  2. Right-click the subclient.
  3. Click Backup.
  4. Click Advanced.
  5. Click Media.
  6. Select Start New Media to start archive operation on a new media.
  7. Select Mark Media Full on Success to mark this media full after the completion of the backup operation.
  8. Select Infinite under Extend Job Retention to retain this job indefinitely.
  9. Select Number of Days to specify the number of days after which this job will be pruned.
  10. Select Storage Policy Default to apply the retention rules of the associated storage policy.
  11. Click OK.
Refer to Creating an Exportable Media Set  and Start New Media for more information.
Allow Other Schedules To Use Media Set This options allows jobs that are part of a schedule policy or schedule and using a specific storage policy to start a new media and also prevent other jobs from writing to the set of media. This option is available only when Start New Media and Mark Media Full options are enabled.
  1. From the CommCell Browser, click Client Computers | SAP For Oracle | < instance name >. The default and other subclients (if available) are displayed on the right-hand window pane.
  2. Right-click the subclient.
  3. Click Backup.
  4. Click Advanced.
  5. Click Media.
  6. Select Allow other Schedules to use the Media Set.
  7. Click OK.
 
Data Path Options Data Protection operations use a specific data path (Library, MediaAgent, Drive Pool, and Drive) to perform the backup operations as configured in the CommCell. By default, the system automatically identifies the data path for the backup operations.
  1. From the CommCell Browser, click Client Computers | SAP For Oracle | < instance name >. The default and other subclients (if available) are displayed on the right-hand window pane.
  2. Right-click the subclient.
  3. Click Backup.
  4. Click Advanced.
  5. Click Data Path.
  6. Select Use MediaAgent and Use Library or Use Drive Pool and Use Drive from the respective drop-down combo boxes.
  7. Click OK.
Refer to Change Data Path for more information.
Vault Tracker The Vault Tracker feature provides the facility to manage media that are removed from a library and stored in offsite locations.
  1. From the CommCell Browser, click Client Computers | SAP For Oracle | < instance name >. The default and other subclients (if available) are displayed on the right-hand window pane.
  2. Right-click the subclient.
  3. Click Backup.
  4. Click Advanced.
  5. Click Vault Tracking.
  6. Select the desired option.
  7. Click OK.
Refer to Vault Tracker documentation for a comprehensive overview prior to using this feature.
Alerts You can configure alerts for a specific backup job.
  1. From the CommCell Browser, click Client Computers | SAP For Oracle | < instance name >.The default and other subclients (if available) are displayed on the right-hand window pane.
  2. Right-click the subclient.
  3. Click Backup.
  4. Click Advanced.
  5. Click Add Alert and it opens Add Alert Wizard window.
  6. From the Add Alert Wizard window, select the Threshold and Notification Criteria.
  7.  Click Next.
  8. Select the Notification Types and Click Next.
  9. Select the Users and User Groups and  Click Next.
  10. Click Finish.
Refer to Alerts and Notifications for more information.