Use the SAP for Oracle optimization feature to reduce the number of snapshots that the software takes during a backup operation.
When you enable the feature, the software takes 3 snapshots of the following volumes and locations:
-
The data volume
-
The log volume
-
The location of the control file
The software skips creating snapshots for the config phase.
The software copies the contents of the following folders to the index:
-
ORACLE_HOME/dbs
-
$SAPDATA_HOME/sapreorg
-
$SAPDATA_HOME/sapbackup
-
$SAPDATA_HOME/saparch
You can further reduce the number of snapshot that the software takes by configuring the software to perform a traditional backup after the IntelliSnap data backup is complete. For more information, see Configuring Subclients for Log Backups.
If you need to specify the location of the SAPBACKUP directory that is under the SAPDATA directory, then you can use the <SID>_sSAPBACKUP. For more information, see Specifying the Location for the SAPBACKUP Directory.
When you enable SNAP optimization, the software copies the configuration files (database init files, BRBACKUP\BRARCHIVE detail files and summary files) to the index . In cases where any of the config files has a size that is greater than 60MB, the software takes additional snapshots.
If you selected the option to create a second copy of the archive redo log (Subclient Properties dialog box, Log Backup tab, Archive Log Second Copy check box), then the software creates an additional snapshot.
The following tables define the snapshots that the software takes.
Online Backups
|
Data |
No |
Additional setting |
Additional setting |
|---|---|---|---|
|
Data detail and summary files location - $SAPDATA_HOME<SID>\oraarch |
SNAPPED |
NOT SNAPPED |
SNAPPED |
|
DATA directory - $SAPDATA_HOME<SID>\oraarch |
SNAPPED |
SNAPPED |
SNAPPED |
|
Log detail and summary files location - $SAPDATA_HOME<SID>\oraarch |
SNAPPED |
NOT SNAPPED |
SNAPPED |
|
Logs directory - $SAPDATA_HOME<SID>\oraarch |
SNAPPED |
SNAPPED |
SNAPPED |
|
Database Init files - $SAPDATA_HOMEdbs |
SNAPPED |
NOT SNAPPED |
NOT SNAPPED |
|
Space reorg file - $SAPDATA_HOME<SID>\oraarch |
SNAPPED |
NOT SNAPPED |
NOT SNAPPED |
|
Ctrl file - $SAPDATA_HOME<SID>\oraarch |
SNAPPED |
SNAPPED |
SNAPPED |
Offline Backups
|
Data |
No |
Additional setting |
Additional setting |
|---|---|---|---|
|
Data detail and summary files location - $SAPDATA_HOME<SID>\oraarch |
SNAPPED |
NOT SNAPPED |
SNAPPED |
|
DATA directory - $SAPDATA_HOME<SID>\oraarch |
SNAPPED |
SNAPPED |
SNAPPED |
|
Log detail and summary files location - $SAPDATA_HOME<SID>\oraarch |
SNAPPED |
NOT SNAPPED |
SNAPPED |
|
Logs Directory - $SAPDATA_HOME<SID>\oraarch |
SNAPPED |
SNAPPED |
SNAPPED |
|
Redo logs directory - $SAPDATA_HOME<SID>\origlog* $SAPDATA_HOME<SID>\mirrlog* |
SNAPPED |
SNAPPED |
SNAPPED |
|
Database Init files - $SAPDATA_HOMEdbs |
SNAPPED |
NOT SNAPPED |
NOT SNAPPED |
|
Space reorg file - $SAPDATA_HOME<SID>\oraarch |
SNAPPED |
NOT SNAPPED |
NOT SNAPPED |
|
Ctrl file - $SAPDATA_HOME<SID>\oraarch |
SNAPPED |
SNAPPED |
SNAPPED |
Procedure
-
To the SAP for Oracle client, add the CV_SAP_SNAP_BKP_OPTIMIZE additional setting as shown in the following table.
For instructions on how to add additional settings from the CommCell Console, see Adding or Modifying Additional Settings from the CommCell Console.
Property
Value
Name
Category
OracleSapAgent
Type
String
Value
Y
Note
From Feature Release (11.16) onwards, the user does not need to place additional setting on client. Optimization is the current default behavior.