Enabling Verification of Oracle Datafiles during a Backup (Snap Integrity Check)
The Snap Integrity Checks are off by default.
The following steps are performed during an IntelliSnap backup without the snap integrity check
- The database is placed in a quiesced state.
- A snapshot is created for data volumes.
- The database is placed in a unquiesced state.
- The snapshot is created for log volumes.
When the Snap Integrity Check is enabled, the following two additional steps are performed after taking snaps.
- The snapshot is mounted on the source and cataloging of datafiles/archived logs is performed from the mounted snapshot. This verifies whether all the datafiles/archived logs are properly captured during an IntelliSnap backup. RMAN catalog datafilecopy checks the datafile header and verify its authenticity before cataloging it.
- Once the catalog is completed, an uncatalog happens and the snapshot is unmounted from the source.
Note: When using ASM databases, during snap integrity check, the snap mount path is appended to the ASM disk string to enable discovery of ASM disks. This does not have any impact on the Oracle database or clients. Also, the check ensures that the modified ASM disk string does not impact the discovery of ASM disks belonging to already existing disk group.
After the snap integrity check is completed, the appended snap mount path in the ASM disk string is retained and can be reused for other IntelliSnap jobs.
- From the CommCell Browser, navigate to Client Computers <Client>| Oracle | <Instance>.
- Right-click the <Oracle Subclient>, and then click Properties.
- On to the IntelliSnap Operations tab of the Subclient Properties dialog box.
Check the Enable Snap Integrity Check check box to enable the feature.
Clear the Enable Snap Integrity Check check box to disable the feature.
- Click OK.
Last modified: 8/28/2018 5:37:14 PM