Backup Flow; Restore Flow - HP Data Protector A.06.11 Integration Manual

For oracle and sap
Hide thumbs Also See for Data Protector A.06.11:
Table of Contents

Advertisement

the backup has finished, the archive logs can either be deleted or kept on the
SAP DB/MaxDB Server, depending on the selected options.
The integration also takes advantage of the concept of SAP DB/MaxDB media and
media groups, thus providing parallel backup and restore of SAP DB/MaxDB objects.
Several SAP DB/MaxDB media are grouped in an SAP DB/MaxDB media group,
which is then backed up or restored in streams. This is referred to as SAP DB/MaxDB
parallelism. See
option.
NOTE:
When running a backup using SAP DB/MaxDB utilities, SAP DB/MaxDB media and
pipes must be configured manually.

Backup flow

When a backup session is started, the Cell Manager starts the sapdbbar with
selected backup parameters from the backup specification. The sapdbbar module
than starts an SAP DB/MaxDB session using the SAP DB/MaxDB dbmcli. The
sapdbbar module issues dbmcli commands that configure SAP DB/MaxDB backup
media (parallelism), configure sapdb_backint and then start the backup using
SAP DB/MaxDB dbmcli. SAP DB/MaxDB then starts the configured
sapdb_backint component. For every SAP DB/MaxDB medium (pipe)
sapdb_backint starts a DMA, which transfers the data from SAP DB/MaxDB
media (pipes) to Data Protector media. This procedure is the same for full, differential,
and transactional backup. Additionally, if the configuration (including media
specification and the backup history) is selected for backup, it is backed up directly
by the sapdbbar module and DMA. The list of configuration files to be backed up
is retrieved through dbmcli.

Restore flow

When a restore session is started, the Cell Manager starts the sapdbbar module,
which starts SAP DB/MaxDB dbmcli. The sapdbbar module issues commands to
SAP DB/MaxDB dbmcli to configure sapdb_backint and SAP DB/MaxDB backup
media (parallelism). SAP DB/MaxDB then starts the configured sapdb_backint,
which starts streaming data to media (pipes) that SAP DB/MaxDB created. For every
SAP DB/MaxDB medium (pipe) the sapdb_backint starts a DMA, which transfers
the data from Data Protector media to SAP DB/MaxDB media (pipes). If
236
Integrating SAP DB/MaxDB and Data Protector
Table 18
for more information on the Data Protector Parallelism

Advertisement

Table of Contents
loading

Table of Contents