Scenario 1 run a stand-alone disk-only backup

Edit online

In this scenario, IBM® Storage Protect Snapshot runs a stand-alone operation for a disk-only backup as IBM Storage Protect for Enterprise Resource Planning is not installed.

In phase 1, IBM Storage Protect Snapshot creates a disk-only snapshot backup of the database files. During phases 2 and 3, the control file, configuration files, and log files are saved to the IBM Storage Protect Snapshot repository.

This scenario demonstrates how the SAP BR*Tool brbackup interacts with IBM Storage Protect Snapshot during backup operations. The SAP BR*Tool brbackup calls backint with these command-line parameters:
-t volume, -t volume_online
IBM Storage Protect Snapshot (backint) uses the snapshot technology available on the snapshot device.
-t file, -t file_online
IBM Storage Protect Snapshot (backint) transfers the Oracle control files into the IBM Storage Protect Snapshot repository. Because IBM Storage Protect for Enterprise Resource Planning is not installed in this scenario, backint is not available in the /usr/sap/<SID>/SYS/exe/run directory. Therefore, the util_path parameter must specify the IBM Storage Protect Snapshot instance directory in the SAP BR*Tools profile (init<SID>.sap).
An SAP BR*Tools backup run is split into three phases:
  1. Back up Oracle database files by using the -t volume | -t volume_online option.
  2. Back up Oracle control files by using the -t file | -t file_online option.
  3. Back up the configuration and log files by using the -t file | -t file_online option.
When IBM Storage Protect Snapshot is configured for stand-alone disk-only backup, IBM Storage Protect Snapshot creates a disk-only snapshot backup of the database files on the storage system. Similarly, a disk-only backup for phase 2 and phase 3 is created by copying the requested files into the IBM Storage Protect Snapshot repository. The configuration in this scenario is for a disk-only backup.
Contents of the SAP BR*Tools profile (init<SID>.sap):
backup_dev_type = util_vol | util_vol_online
util_par_file = <ACS_DIR>/profile
util_path = <instance_directory>

In the SAP BR*Tools profile, init<SID>.sap, the util_path parameter must point to the IBM Storage Protect Snapshot instance directory. The util_par_file must point to the IBM Storage Protect Snapshot profile.

Settings of the IBM Storage Protect Snapshot profile (<ACS_DIR>/profile):
TSM_BACKUP   NO

However, such an operation must not be run unless necessary because the Oracle control files and other files are transferred into the repository. These additional files in the IBM Storage Protect Snapshot repository can cause performance issues that are related to back up, restore, and space availability. Even for disk-only backups, an integration with IBM Storage Protect or a third-party tape backup product is the preferred solution. For more information about this solution, see Scenario 2.