Filter
Top Products
Integrating SAP R/3 and Data Protector
Integration Concept
Chapter 2154
3. The backint program obtains the SAP R/3 configuration from the Cell
Manager, divides the files for backup into subsets (provided that the
specified concurrency is greater than 1) and starts the sapback
program for each subset. Each sapback process connects to the BSM,
which then starts General Media Agents on the corresponding client
systems and establishes a connection between the sapback processes
and General Media Agents.
Data transfer can begin at this point. The sapback processes read
data from disks and send it to General Media Agents. The first
backint program stops as soon as all sapback processes have finished
and control is returned to the parent process, either the BRBACKUP
or BRARCHIVE utility.
The second backint command is initiated by either the BRBACKUP
or BRARCHIVE command. This command attempts to back up the
SAP R/3 log files and parameter files (in the case of BRBACKUP), or
the archived redo logs (in the case of BRARCHIVE) that have been
created since the first backint command.
If new archived redo logs have been created, they are backed up and
another backint command is started. Otherwise, the SAP R/3 log files
and the parameter files are backed up, and the second backint
program is started using BRBACKUP.
Therefore, more than two backint commands may be initiated by
BRARCHIVE, while there are only two backint commands initiated
by BRBACKUP.
If archive logs were backed up, omnisap creates a copy of the control
files either in the directory defined by the SAPBACKUP variable, or
in /var/opt/omni/tmp (on UNIX) or
<Data_Protector_home>\tmp (on Windows) if the variable is not
set. The control file is then backed up by the backint utility using
sapbackup.
NOTE The total number of sapback processes started in one session using Data
Protector is limited to 256.
4. General Media Agents finish transferring data when all the sapback
processes are complete. When all of the General Media Agents have
finished data transfer, the BSM waits for a timeout