Restore Flow; Data Protector Sap R/3 Configuration File - HP Data Protector A.06.11 Integration Manual

Restore flow

You can start a restore using the Data Protector user interface or SAP BRTOOLS user
interface. However, only a standard filesystem restore can be performed using Data
Protector.
1. When you select objects to be restored and start a restore using SAP BRTOOLS,
the following happens (depending on which mode you use):
• Backint mode: BRRESTORE checks if enough free disk space is available and
starts a backint command to restore Oracle data files.
If the backups of files to be restored reside on different media, backint starts
a separate saprest process for each medium, so that the files are restored
in parallel (provided that the specified concurrency is large enough). The
first saprest process starts a RSM, while the subsequent saprest processes
connect to the same RSM. RSM checks if the restore devices are available
and starts the data flow.
• RMAN mode: BRRESTORE starts RMAN, which connects to Data Protector
via Data Protector Database Library and Oracle Server processes and enables
data transfer of Oracle data files.
2. When all the General Media Agents finish with data transfer, the RSM waits for
a timeout (SmWaitForNewClient global variable) and completes the restore
session if no backint command is started within this time frame.

Data Protector SAP R/3 configuration file

Data Protector stores the integration parameters for every configured SAP R/3
database in the following file on the Cell Manager:
• On UNIX:
/etc/opt/omni/server/integ/config/SAP/client_name%ORACLE_SID
• On Windows:
Data_Protector_home\Config\Server\Integ\Config\Sap\client_name%ORACLE_SID
The parameters stored are:
• Oracle home directory
• encoded connection string to the target database
• BRTOOLS home directory
• the variables which need to be exported prior to starting a backup
• SAPDATA home directory
160 Integrating SAP R/3 and Data Protector