Data Aging from the CommCell Console for Oracle

If you run data aging from the CommCell Console, it checks for qualifying jobs after checking the basic retention rule, log rule and any extended rule. If any job qualifies for data aging, it generates an RMAN script to make the aged backup pieces unavailable.

Example

The script below is a sample RMAN script.

allocate channel for maintenance type 'sbt_tape' PARMS="SBT_LIBRARY=/opt/snapprotect/Base/libobk.so"
TRACE 0;
change backuppiece 'obpb5ojv_1_1','c-1013501923-20140618-00' unavailable;
change backuppiece 'odpb5ot3_1_1','c-1013501923-20140618-01' unavailable;
release channel;
exit;

Deleting Backup Pieces from the Oracle Recovery Catalog

When a Data Aging job runs, it issues the change backuppiece... UNAVAILABLE command to RMAN to disable the backup pieces in the Oracle Recovery Catalog database that were pruned from the Media Manager CommServe tables. To delete backup pieces from the Recovery Catalog instead of marking them unavailable, create and set the OracleDeleteAgedBackupPiece additional setting to Y, which generates the following RMAN script.

allocate channel for maintenance type 'sbt_tape' PARMS="SBT_LIBRARY=/opt/snapprotect/Base/libobk.so"
TRACE 0;
change backuppiece 'obpb5ojv_1_1','c-1013501923-20140618-00' delete;
change backuppiece 'odpb5ot3_1_1','c-1013501923-20140618-01' delete;
release channel;
exit;

Timeout for Oracle Crosscheck for an Instance During Data Aging

By default the timeout for the Oracle CROSSCHECK per instance is 600 seconds during the data aging operation. If a CROSSCHECK timeout occurs, data aging does not remove the backup pieces from the CommServe database. If there are a large number of backup pieces that need to be aged for the instance, modify the timeout value, or disable the option by using the OraCrossCheckTimeOut additional setting.

Disabling the Oracle RMAN Crosscheck During Data Aging

By default, during a data aging operation, an Oracle CROSSCHECK is performed by the system to synchronize the entries in the CommServe database with the Recovery Catalog. If required, disable this CROSSCHECK operation using the Disable RMAN Cross Check option in the Instance Properties (Details) tab for the specific Oracle instance.

  1. From the CommCell Browser, expand Client Computers > client > Oracle.
  2. Right-click the instance and then click Properties.
  3. On Details tab of the Instance Properties dialog box:
    • Select the Disable RMAN cross check check box.
    • Click OK to close the warning message.
  4. Click OK to close the Instance Properties dialog box.

Synchronizing the CommServe Database and Oracle Recovery Catalog

Sometimes data aging removes the backup pieces from the CommServe database but not from the Recovery Catalog. In such cases, you need to manually run the Oracle CROSSCHECK command on the client side to synchronize both the CommServe database and the Oracle Recovery Catalog.

Run this in the following cases.

  1. If the Oracle Services are down while data aging runs.
  2. If any of the backup pieces are manually deleted from the Oracle Recovery Catalog.
  3. If the SnapProtect software is uninstalled on the client.

Preventing RMAN Command Line Scripts from Deleting RMAN Backups

The CommCell data aging feature ages and deletes backups according to user-defined rules.

Users can also delete the backups using RMAN Command Line scripts before the data aging rules take effect.

You can prevent RMAN Command Line scripts from deleting the SnapProtect backups.

  • On the CommServe computer, add the DisableRMANPruning additional setting and configure the following values:
    Property Value
    Name DisableRMANPruning
    Category CommServDB.GxGlobalParam
    Type Integer
    Value 1

    For instructions on how to add additional settings from the CommCell Console, see Add or Modify an Additional Setting.

Related Topics

Data Aging for Oracle

Retention Rules for Oracle

Data Aging from the RMAN Command Line

Data Aging