Filter
Top Products
Integrating SAP R/3 and Data Protector
Configuring the Integration
Chapter 2168
integration. However, you need to create a link to the Data Protector
backint interface on all other nodes. Enter the following command on all
other nodes:
ln -s /opt/omni/lbin/backint \
/usr/sap/<ORACLE_SID>/sys/exe/run
In a cluster environment, the environment variable OB2BARHOSTNAME
must be defined as the virtual hostname before running the
configuration from the command line (on the client). The
OB2BARHOSTNAME variable is set as follows:
• On UNIX: export OB2BARHOSTNAME=<virtual_hostname>
• On Windows: set OB2BARHOSTNAME=<virtual_hostname>
Add the SAP R/3 group dba user to Data Protector for the virtual server
and for every node in the cluster.
For information on how to add a user to a user group, see the online Help
index: “adding users”.
For information on the Data Protector Cell Manager package
configuration (if you want to install and configure the Data Protector
Cell Manager in the MC/SG cluster), see the online Help index
“MC/ServiceGuard integration”.
Cluster-Aware
Clients on
Windows
The client configuration must be performed on only one of the cluster
nodes per one SAP R/3 server, since the Data Protector SAP R/3
configuration file resides on the Cell Manager.
However, the Data Protector backint program needs to be manually
copied to the correct location on all other nodes. On every other node,
copy the <Data_Protector_home>\bin\backint.exe to the directory
where the SAP R/3 backup utilities reside.
NOTE Each SAP R/3 instance must be configured separately.