3. The Data Protector ob2smbsplit command resolves the backup configuration,
creates a replica, and preparing the replica for backup.
The mountpoints for the backed up object are created on the backup system.
The backup volume/disk groups are activated and the filesystems are mounted
on the backup system.
4.
ZDB to disk only:
The remaining ZDB options are processed and the details on
the session are written to the ZDB database. The session then finishes.
5.
ZDB to tape, ZDB to disk+tape:
BRBACKUP starts the Data Protector backint
program, which starts establishing a connection between the Data Protector
Data Movement Agents (DMA) on the backup system and the General Media
Agents (MA). The process is coordinated by the Data Protector Backup Session
Manager (BSM). When the connection is established, the data specified for
backup is streamed to tape.
6. When the data transfer completes, the backup system is disabled (filesystems
are unmounted on all platforms and volume/disk groups deactivated on UNIX).
7.
EMC and XP only:
Links are re-established, depending on how ZDB options are
specified.
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
• user name and user group
• temporary directory used for the copy of the control file or redo logs
• list of control files and redo logs that will be copied to a safe location
Zero downtime backup integration guide 167
To Next Page
Loading...
