Loading...

Advanced Backup - Oracle RAC iDataAgent

Table of Contents

Data in Backups

The following data is included in Oracle RAC backups:

  • The Oracle database files that include datafiles (*.dbf) and backup control files (*.ctl)
  • The archived redo logs
  • The parameter files (SP File)
  • The block changes tracking file

The following data is not included in an Oracle RAC backup:

  • Oracle Cluster Voting Disk
  • Oracle Cluster Registry (OCR)
  • OCR Log Files

Full Backups

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.

Data that is backed up for any Oracle instance configured on the Oracle RAC node is lost if you delete the configured Oracle instance.

Procedure

  1. From the CommCell Browser, expand Client Computers > client > Oracle RAC > instance.
  2. Right-click the subclient and click Backup.
  3. On the Backup Options for Subclient dialog box, select the backup type and job initiation:
    1. In the Backup Type section, select Full.
    2. If you selected the Cumulative check box, specify the backup incremental level in the Oracle Incremental Level box.
    3. In the Job Initiation section, specify whether to run the backup now or if it will be scheduled.

      Note: If you selected Schedule, set up the schedule.

      For information on configuring a backup schedule, see Schedule Backups.

  4. Optional: Uniquely identify a backup.
    1. Click Advanced.

      The Advanced Backup Options dialog box appears.

    2. On the Oracle Options tab, in the Backup Tag box, enter a unique tag.

      You can include variables in the tag. For supported tag variables, see Oracle Tag Variables.

    3. Click OK to close the Advanced Backup Options dialog box.
  5. Optional: View or customize the RMAN script that is generated from the selected options. For instructions, see Viewing Backup RMAN Scripts and Customizing Backup RMAN Scripts.
  6. Click OK to close the Backup Options dialog box.

Incremental Backups

An Oracle incremental backup contains the changed data from the last full backup. Incremental backups use less media and resources than full backups.

In a cumulative level n backup, only the data that differs from the most recent backup at level n-1 or lower, is backed up.

For more information, see Incremental.

Procedure

  1. From the CommCell Browser, expand Client Computers > client > Oracle RAC > instance.
  2. Right-click the subclient and click Backup.
  3. On the Backup Options for Subclient dialog box, select the backup type and job initiation:
    1. In the Backup Type section, choose the backup type.
    2. If you selected the Cumulative check box, specify the backup incremental level in the Oracle Incremental Level box.
    3. In the Job Initiation section, specify whether to run the backup now or if it will be scheduled.

      Note: If you selected Schedule, set up the schedule.

      For information on configuring a backup schedule, see Schedule Backups.

  4. Optional: Uniquely identify a backup.
    1. Click Advanced.
    2. On the Advanced Backup Options dialog box, click the Oracle Options tab, in the Backup Tag box enter a unique tag.

      You can include variables in the tag. For supported tag variables, see Oracle Tag Variables.

      The Oracle tag you that you specify for the backup overrides the tag defined for the subclient.

    3. Click OK to close the Advanced Backup Options dialog box.
  5. Optional: Set the backup load distribution across disks. For more information, see Configuring the Disk Ratio for Oracle RMAN.
  6. Optional: View or customize the RMAN script that is generated from the selected options. For instructions, see Viewing Backup RMAN Scripts and Customizing Backup RMAN Scripts.
  7. Click OK to close the Backup Options dialog box.

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.
  • The subclient must be configured for archive log backups. See Creating A Subclient for Log Backups for instructions on how to create a separate subclient for archive logs.

Best Practice: Configure a schedule to back up the logs before the archive log destination fills up to 80% of the space (Backup Task Options dialog box, Schedule Pattern tab, Start back when disk is box). For information on how to configure an automatic schedule, see Creating an Automatic Schedule for Database Log Backups.

Procedure

  1. From the CommCell Browser, expand Client Computers > client > Oracle > instance.
  2. Right-click the subclient configured for the archive log backup and then click Backup.
  3. On the Backup Options for Subclient dialog box, select the backup type and initiation:
    1. In the Backup Type section, choose the backup type.
    2. If you selected the Cumulative check box, specify the backup incremental level in the Oracle Incremental Level box.
    3. In the Job Initiation section, specify whether to run the backup now or if it will be scheduled.

      Note: If you selected Schedule, set up the schedule.

      For information on configuring a backup schedule, see Schedule Backups.

    4. Click Advanced.

      The Advanced Backup Options dialog box appears.

  4. Select the option to determine the logs to back up and delete.

    On the Backup Archive Logs tab, and Delete Archive Logs tab:

    Select the Delete Archive Logs check box and Backup Archive Logs check box.

    Choice Description
    All Backs up or deletes all logs
    Older than n Days Backs up or deletes logs older than the specified number of days
    Not Older than n Days Backs up or deletes logs not older than the specified number of days
    By Log Time Backs up or deletes logs in the specified time range.

    Select the Start Time and End Time check boxes and enter the start and end times of the logs.

    If you only specify the start log time, all logs are backed up from the start time to the current time.

    By Log Seq Num Backs up or deletes logs in a specified sequence range.

    The 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 number1. When the first file fills, Oracle switches to the second file and assigns a log sequence number of 2.

    Select the Start Sequence Number and End Sequence Number check boxes and enter the beginning and ending sequence numbers

    By Sys change Num Backs up or deletes logs in the specified System Change Number range.

    The 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 committed transactions could be 576601 and 576799.

    Select the Start Sys chg Num and End Sys chg Num check boxes and enter the beginning and ending SCNs:

    The end serial number must be greater than or equal to the start serial number. •

    The start and the end SCN cannot be 0.

    If you provide only the start SCN, is the only one provided, only the logs starting that start from that sequence number are backed up.

    Like Backs up or deletes logs with a file name that starts with a specified string.

    Enter the string to match.

    Not Backed up Backs up or deletes logs that have not been backed up a specified number of times.

    Enter the number of times a log must be backed up.

  5. On the Backup Archive Logs tab, specify the location where the backed up logs are stored:
    1. Select the Archive Log Destinations for Backup check box.
    2. Click Add.
    3. On the Select an Archive Log Destination dialog box enter the full path to the directory where backed up archive logs will be stored.
    4. Click OK to close the Select an Archive Log Destination dialog box.
  6. Optional: Uniquely identify a backup. On the Oracle Options tab, enter a unique tag.

    You can include variables in the tag. For supported tag variables, see Oracle Tag Variables.

    The Oracle tag you that you specify for the backup overrides the tag defined for the subclient.

  7. Optional: Set the backup load distribution across disks to improve performance. For more information, see Configuring the Disk Ratio for Oracle RMAN.
  8. Click OK to close the Advanced Backup Options dialog box.
  9. Click OK to close the Backup Options dialog box.

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.

Use control file backups to create standby databases from the CommCell Console. Standby databases are used during database recovery.

Before You Begin

  1. Configure a subclient that contains the control file.
  2. Optional: Configure Job Throttling for an Oracle Client.

Procedure

  1. From the CommCell Browser, expand Client Computers > client > Oracle > instance.
  2. Right-click the subclient configured for control file backup, and click Backup.
  3. On the Backup Options for Subclient dialog box, select the backup type and initiation:
    1. In the Backup Type section, choose the backup type.
    2. If you selected the Cumulative check box, specify the backup incremental level in the Oracle Incremental Level box.
    3. In the Job Initiation section, specify whether to run the backup now or if it will be scheduled.

      Note: If you selected Schedule, set up the schedule.

      For information on configuring a backup schedule, see Schedule Backups.

    4. Click Advanced.

      The Advanced Backup Options dialog box appears.

  4. On the Oracle Options tab:
    1. Select the Backup Control File for Creating Standby Database check box.
    2. Optional: Uniquely identify a backup. In the Backup Tag box, enter a unique tag.

      You can include variables in the tag. For supported tag variables, see Oracle Tag Variables.

      The Oracle tag that you specify for the backup overrides the tag defined for the subclient.

    3. Click OK to close the Advanced Backup Options dialog box.
  5. Optional: Set the backup load distribution across disks to improve performance. For more information, see Configuring the Disk Ratio for Oracle RMAN.
  6. Optional: View or customize the RMAN script that is generated from the selected options. For instructions, see Viewing Backup RMAN Scripts and Customizing Backup RMAN Scripts.
  7. Click OK to close the Backup Options dialog box.

Container and Pluggable Database Backups

Oracle 12c supports container and pluggable databases. SnapProtect 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.

  1. Add an instance for the container database.
  2. 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

  1. 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;

  2. Execute the RMAN script. See Running RMAN Scripts from Third Party Command Line.

Backing Up Multiple Pluggable Databases

  1. 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;

  2. Execute the RMAN script. See Running RMAN Scripts from Third Party Command Line.

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.

  1. From the CommCell Browser, navigate to Client Computers | <RAC Client> | <Instance>.
  2. Right-click the <Subclient> and click Backup.
  3. Click Script Preview.
  4. 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.

  1. From the CommCell Browser, navigate to Client Computers | <RAC Client> | <Instance>.
  2. Right-click the <Subclient> configured for archive log backup, and then click Backup.
  3. Click Advanced.
  1. Click the Custom RMAN script tab.
  2. Select the Customize script check box.
  3. Edit the RMAN script as required, and then click OK.
Follow the steps given below to schedule a backup:

Cataloging RMAN Backup Pieces

When the Oracle recovery catalog does not know about the backup pieces you want to restore, you can run this procedure to add the backup pieces from the tape or media to the Oracle recovery catalog.

  1. On the RMAN command line, create and run an RMAN script similar to the one below.

    For information on the supported SBT parameters, see SBT Parameters.

    configure channel device type 'sbt_tape' PARMS="SBT_LIBRARY=software_install_path/Base/libobk.so,ENV=(CVOraRacDBName=<DBName>)”;

    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)
    • 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
  2. On the RMAN command line, type the following command to verify the configuration.

    RMAN>show all;

  3. On the RMAN command line, type the following command to catalog the backup pieces.

    catalog device ‘sbt_tape’ backuppiece ‘backuppiecename1’,‘backuppiecename2’;

Performing Parallel Backups with Multiple DataPaths for Load Sharing

Sometimes, the resources on a single datapath may not be enough to perform a backup job. When you configure a primary storage policy copy with multiple datapaths and perform a backup, this backup job can get the reservations from multiple datapaths that are present in the primary copy. This will share the load of your backups between multiple DataPaths.

  1. From the CommCell Browser, navigate to Client Computers | <RAC Client> | <Instance>.
  2. Right-click the <Subclient> and click Backup.
  3. Select backup type and click Immediate to run the job immediately.
  4. Click OK.

Example of JM Log with RM Messages enabled:

9272 e38 05/02 16:14:00 33080 Database Added new stream. (dest)RCID [53989] Reservation Id [60368] Stream Number [1] Copy Id [95] Is Primary [true] srcRCId [0] srcResvId [0] srcCopyId [0]. 9272 e38 05/02 16:14:00 33080 JobSvr Obj CVBkpJobSvr::updateInfo(rcid=53989),setMediaInfo(dbserve12) 9272 14c 05/02 16:14:00 33080 Database Added new stream. (dest)RCID [53987] Reservation Id [60366] Stream Number [2] Copy Id [95] Is Primary [true] srcRCId [0] srcResvId [0] srcCopyId [0]. 9272 14c 05/02 16:14:00 33080 JobSvr Obj CVBkpJobSvr::updateInfo(rcid=53987),setMediaInfo(dbserve12) 9272 e38 05/02 16:14:00 33080 Database Added new stream. (dest)RCID [53988] Reservation Id [60367] Stream Number [3] Copy Id [95] Is Primary [true] srcRCId [0] srcResvId [0] srcCopyId [0]. 9272 e38 05/02 16:14:00 33080 JobSvr Obj CVBkpJobSvr::updateInfo(rcid=53988),setMediaInfo(dbserve12) 9272 14c 05/02 16:14:00 33080 Database Added new stream. (dest)RCID [53990] Reservation Id [60369] Stream Number [4] Copy Id [95] Is Primary [true] srcRCId [0] srcResvId [0] srcCopyId [0]. 9272 14c 05/02 16:14:00 33080 JobSvr Obj CVBkpJobSvr::updateInfo(rcid=53990),setMediaInfo(dbserve12) 9272 e38 05/02 16:15:38 33080 Resource Removed resource user 53987 9272 e38 05/02 16:15:38 33080 Resource Removed resource user 53988 9272 e38 05/02 16:15:38 33080 Resource Removed resource user 53989 9272 e38 05/02 16:15:38 33080 Resource Removed resource user 53990

 

Configuring the Disk Ratio for Oracle RMAN

The Oracle disk ratio groups the data files into backup sets, distributes the backup load across the disks and enhances backup performance.

The restore performance is slower when a larger number of disks are grouped together, so set the disk ratio to a minimum.

By default, the RMAN disk ratio is not set.

Procedure

  1. From the CommCell Browser, expand Client Computers > client > Oracle RAC > instance.
  2. Right-click the subclient and click Backup.
  3. On the Backup Options dialog box click Advanced.

    The Advanced Backup Options dialog box appears.

  4. On the Oracle Options tab:
    1. Select the Enable RMAN Disk Ratio check box.
    2. Select the number of disks for the backup, in the No. of Disks box, type the number of disks.
    3. Click OK to close the Advanced Backup Options dialog box.
  5. Click OK to close the Backup Options dialog box.

Example

If data files are distributed across 10 disks that supply data at 10 bytes/second and a tape drive that needs 50 bytes/second to keep streaming, set the disk ratio value to 5. This value directs RMAN to include data files from 5 disks in each backup set.

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:

  1. From the CommCell Browser, navigate to Client Computers | <RAC Client> | <Instance>.
  2. Right-click the <Subclient>, and then click Properties.
  3. Click the Advanced tab, and then click the Options tab.
  4. Select the Validate check box.
  5. Click OK.
 

Managing Jobs

For information on how to manage the job, see Job Controller Overview.