Profile Parameters and BRBACKUP Command Options 

SAVESET Grouping and Preparation Run

To define the size of the savesets by the number of files they contain, make the following entry in the initialization file init<DBSID>.sap :

The corresponding command option is: brbackup -s | -savesets

You can start the preparation run for determining the optimum distribution of files across the savesets as follows:

RMAN Backup with the SAP Backup Library

For backups with the SAP backup library you need to make the following special entries in the initialization file init<DBSID>.sap or set the corresponding command options:

RMAN Backup with an External Backup Library

For backups with external backup libraries, you need to make the following entries in the initialization profile init<DBSID>.sap or the corresponding command options:

You can set other parameters as well, which BRBACKUP sends directly to the Oracle RMAN (without the prefix rman_ ). These parameters affect how the savesets are formed and the parallel backup to different media.

Number of channels allocated to the parallel processes

controls the number of files in each saveset; default: 0 (one files in each saveset for normal backups; all files in one saveset for incremental backups)

For more information on these parameters, see the Oracle8 Server – Release 8.0 Backup and Recovery Guide.

RMAN Backups Without Backup Library

For normal backups to disk with RMAN, you need to make the following entries in the initialization file init<DBSID>.sap or the corresponding command options:

The individual steps of the incremental backup strategy without backup library have the following command options:

  1. Full backup (level 0) without RMAN:
  1. Incremental backup (level 1)to disk with RMAN:
  1. Backup of the incremental backup to tape without RMAN (two-phase backup):

Restoring Incremental Backups

To make the database consistent again, for example after a media error, you can use the following BRRESTORE command (RMAN adjusts the changes in the files that have been affected):

  1. If necessary: Restoration of the control file and the online redo log files from the last incremental backup:
  1. Restoration of a full backup (level 0):
  1. Restoration of the last incremental backup (level 1):
  1. Import of the offline redo log files with the Oracle Server Manager.

Restoring Incremental Backups with Structural Changes

In an incremental backup with structural changes, the new files are backed up in full to a second saveset in subsequent incremental backups. The following savesets are created if the SAP backup library is used:

The backup of the new files to a separate saveset allows a precise specification of which files are to be restored.

Restoration of changes to all files that were in the database at the time of the last full backup (level 0) (first saveset of the last incremental backup):

Restoration of the files that have been added since the last full (level 0) (second saveset of the last incremental backup):

Restoration of the whole incremental backup (both savesets, if they exist):

 

More information:

Oracle8 Server – Release 8.0 Backup and Recovery Guide