Filter
Top Products
Integrating SAP R/3 and Data Protector
Integration Concept
Chapter 2 157
The restore session proceeds according to the following stages if the
restore is performed in backint mode.
1. Using the SAPDBA utility, the objects to be restored are selected.
2. The BRRESTORE first checks whether the required free disk space is
available to allow the files to be restored. It then starts the first
backint command to restore the Oracle Target Database’s data files.
The backint command reads the SAP R/3 configuration file, divides
the files for restore into subsets (provided that the specified
concurrency is greater than 1) and starts the saprest process for
each subset.
The first saprest process starts the Data Protector Restore Session
Manager (RSM), while the subsequent saprest processes connect to
the same RSM. In addition, the saprest process checks whether the
specified objects have been backed up.
The RSM checks the availability of the restore devices, starts General
Media Agents and establishes a connection between the saprest
processes and General Media Agents. Data transfer begins at this
stage. Data is sent from the media to the target disks. The General
Media Agent finishes as soon as all saprest processes connected to it
are completed.
3. When all the General Media Agents have finished, the RSM waits for
a timeout (SmWaitForNewClient global variable) and completes the
restore session, if no backint is started within this time frame.
Restore Flow
Using Recovery
Manager
A restore session using RMAN differs from a restore session using the
backint mode in the step 2 as follows:
BRRESTORE starts RMAN in order to restore the Oracle Target
Database data files. RMAN then connects to the Data Protector
Database Library via the Oracle Server processes.