Filter
Top Products
Integrating SAP R/3 and Data Protector
Configuring an SAP R/3 Backup
Chapter 2188
influences (such as mount prompts),
and is therefore best for
environments with large libraries of
the same quality. Each subset is
backed up by one Data Protector
sapback program, thus allowing
concurrent backup of all subsets of
the same type. Data Protector
automatically stores backup speed
information in the speed section of
the Data Protector integration
configuration file on the Cell
Manager. It uses this information to
optimize backup time.
This type of balancing may lead to
non-optimal grouping of files in the
case of online backup, or if the speed
of backup devices varies significantly
among devices.
Balancing: Manual Manual balancing optimizes backups
by allowing you to group files into
subsets and back up these subsets
using specific devices. See “Manual
Balancing of Files into Subsets” on
page 193 for more information.
Balancing: None No balancing is used. The files are
backed up in the same order as they
are listed in the internal Oracle
database structure. To check the
order use the Oracle Server Manager
SQL command: select * from
dba_data_files
Pre-exec Specifies an object pre-exec command
with options that will be started on
the SAP R/3 Database Server before
backup. The command/script is
started by Data Protector
omnisap.exe and has to reside in the
<Data_Protector_home>\bin
(Windows systems), /opt/omni/bin