HP A.06.11 - Manual (Page 159)

2. BRBACKUP does the following:
• Changes the state of the Oracle Target Database (opened or closed),
according to the backup type (online or offline).
• Switches the Oracle Target Database to the ARCHIVELOG mode.
The archived redo log files are written to the archiving directory by Oracle
and are backed up later using BRARCHIVE.
• Creates the BRBACKUP log during the backup session, which contains
information about backed up files and the backup ID. This information is
needed to determine the location of the database files and archived redo
log files during restore.
• Sets the tablespace mode (BEGIN / END BACKUP) in the case of online
backup using backint. In this way, the SAP R/3 application puts a tablespace
in the backup mode just before it is backed up and returns it to the normal
mode immediately after the backup completes.
3. • If BRBACKUP is started:
a. BRBACKUP starts a backint command (backint mode) or RMAN (RMAN
mode), which backs up Oracle data files and control files.
b. BRBACKUP starts a backint command (in the backint and RMAN mode),
which backs up the SAP parameter file and the SAP R/3 history files
that have been created during the backup of Oracle data files and
control files.
• If BRARCHIVE is started (in the backint or RMAN mode), BRARCHIVE starts
a backint command, which backs up archived redo log files. In addition, a
copy of control files is created, which is also backed up.
NOTE:
Backint divides the files specified for backup into subsets according to the
selected balancing type and starts a sapback process for each subset
(provided that the specified concurrency is large enough). The sapback
processes read data from disks and send it to General Media Agents.
4. When all the General Media Agents finish with data transfer, the BSM waits for
a timeout (SmWaitForNewClient omnirc global variable) and completes the
backup session if no backint command is started within this time frame.
Integration guide for Oracle and SAP 159