Before You Begin It is recommended that you configure and run a Data Protector test filesystem backup of the SAP R/3 Database Server (a client system in the Data Protector cell).
In case of problems, this type of backup is much easier to troubleshoot than the integration itself.
A test filesystem backup includes installing a Disk Agent on the SAP R/3 Database Server. Any device can be used for the test purposes only.
Configure a standard filesystem backup, which can include one directory only. The test should include a partial restore to the SAP R/3 Database Server as well.
Refer to the HP OpenView Storage Data Protector Administrator’s Guide for detailed instructions about filesystem backups.
Configuring the SAP R/3 Database Server involves preparing the environment for performing backups. The environment parameters such as the Oracle home directory and the connection string to the Oracle Target Database are saved on the Cell Manager. The database must be online during the configuration procedure.
Cluster-Aware Clients on Windows/UNIX
You also need to edit the Data Protector omnirc file on each cluster node and specify the name of the cluster node in the SAPLOCALHOST variable. Below you see an example of the omnirc file:
# SAP R/3 related entries for clustering
#
SAPLOCALHOST=<cluster_node_name>
NOTE Make sure that the SAPLOCALHOST variable is not defined in the Environment section of the Data Protector SAP R/3 configuration file.
Refer to “Data Protector SAP R/3 Configuration File” on page 155 for information on how to do that.
Cluster-Aware Clients on UNIX
When configuring the Data Protector SAP R/3 integration, configure it only on 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. Use
the virtual hostname when configuring the 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. Refer to HP OpenView Storage Data Protector Administrator’s Guide for information on how to add a user to Data Protector.
For information on the Data Protector Cell Manager package
configuration (if you want to install and configure an Data Protector Cell Manager in the MC/SG cluster), refer also to the HP OpenView Storage Data Protector Administrator’s Guide.
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.
NOTE Make sure to set any Oracle and SAP R/3 related environment variables needed for the Oracle and SAP R/3 databases to function properly (for example, the Oracle NLS_LANG environment variable) on the SAP R/3 Database Server. Refer to the Oracle and SAP R/3 documentation for more information.
Data Protector Inet User Account on Windows
On Windows, set the service startup account of the Data Protector Inet service as an SAP administrator account. To configure the Data Protector Inet service startup account, go to Control Panel, then Administrative Tools, Services. Double-click the Inet service to configure it. This user must also be included in the ORA_DBA local group on the system where SAP R/3 instance is running.
Configuration of an SAP R/3 Database Server is performed using the
<Data_Protector_home>\bin\util_sap.exe (Windows systems), /opt/omni/lbin/util_sap.exe (HP-UX and Solaris systems), or /usr/omni/bin/util_sap.exe (other UNIX systems) command.
On Windows, configuration can be started remotely using the Data Protector GUI from any Data Protector Windows client within the same Data Protector cell, or locally on the SAP R/3 Database Server.
The util_sap.exe Command
Use the util_sap.exe command to get the information you may need to configure your SAP R/3 Database Server. This will:
• List all Oracle instances on a particular system.
util_sap.exe -APP
• List the tablespaces that belong to a particular Oracle instance:
util_sap.exe -OBJS0 <ORACLE_SID>
• List the database files that belong to a particular tablespace of the Oracle instance:
util_sap.exe -OBJS1 <ORACLE_SID> <TABLESPACE>
Using the CLI - UNIX Systems Only
On UNIX, to configure an SAP R/3 Database Server, execute the
following command with root privileges on the SAP R/3 Database Server:
NOTE Each instance must be configured separately.
util_sap.exe -CONFIG <ORACLE_SID> <ORACLE_HOME> \
<targetdb_connection_string> <SAPTOOLS_DIR> \ [<SAPDATA_HOME>], where:
• <ORACLE_SID>
is the is the name of the Oracle database instance to be configured
• <ORACLE_HOME>
is the directory in which Oracle binaries are installed
• <targetdb_connection_string>
is the login information to the target database of the
<user_name>/<password>@<service> format, described in
“Glossary” on page G-1.
The <user_name> is the name by which a user is known to Oracle Server and to other users. Every user is identified by a password, and both must be entered to connect to an Oracle database. This user is, by default, used by brbackup and brarchive during backup. To define a different user when backing up, use the -u <user_name> as a BR Backup SAP R/3 backup option. See “SAP R/3 Specific Backup Options” on page 183.
NOTE The user <user_name> is visible during backup when the ps -ef command is run.
• <SAPTOOLS_DIR>
is the directory in which SAP R/3 backup utilities are stored. SAP recommends to install SAP R/3 backup utilities on both local nodes in the cluster in case the application is cluster-aware.
Directory where SAP R/3 database files are installed. This is an optional parameter. By default, it is set to <ORACLE_HOME>.
Using the GUI To configure an instance of the SAP R/3 Database Server, perform the following steps using the Data Protector GUI:
1. In the Data Protector Manager, switch to the Backup context.
2. In the Scoping Pane, expand Backup, then expand Backup Specifications, and right-click SAP R/3.
3. Click Add Backup. In the Create New Backup dialog box, double-click the Blank SAP Backup template or any of the pre-defined templates.
The properties of a particular backup template can be seen in the corresponding pop-up window.
4. In the Results Area of the next page of the wizard, enter the following information:
• Name of the SAP R/3 Database Server you want to configure. If the application is cluster-aware, select the virtual server of the SAP R/3 resource group.
• Name of the Oracle Server instance (ORACLE_SID) on which the SAP R/3 Database Server is running.
• On UNIX, enter also the UNIX user name and user group of the SAP R/3 user, as described in “Configuring an SAP R/3 User in Data Protector (UNIX Systems Only)” on page 162.
Figure 2-5 Specifying the SAP R/3 Database Server and the Oracle SID on Windows
Figure 2-6 Specifying the SAP R/3 Database Server and the Oracle SID on UNIX
Once you have provided the required information, click Next. If the selected system is configured for the first time, the configuration window is displayed.
Figure 2-7 Configuring an SAP R/3 Database Server on Windows
Figure 2-8 Configuring an SAP R/3 Database Server on UNIX
5. Enter the following information in the Configure SAP dialog box:
• The Oracle Server home directory. If not specified, this is set to the default Oracle home directory.
• SAP data home directory (if not entered, this is set to
<ORACLE_HOME>)
• The connection string to the Oracle Target Database.
See “Glossary” on page G-1 for more information on login connection strings.
• The directory where the SAP R/3 backup utilities are stored. By default, the utilities reside in the
\\<SAP_system>\sapmnt\<ORACLE_SID>\sys\exe\run (Windows systems) or /usr/sap/<ORACLE_SID>/SYS/exe/run (UNIX systems) directory.
What Happens? The following happens after saving the configuration.
Data Protector starts the util_sap.exe file on the SAP R/3 Database Server, which performs the following:
1. Saves the configuration parameters in the Data Protector integration configuration on the Cell Manager in the
/etc/opt/omni/server/integ/config/SAP/<client_name>%<
ORACLE_SID> file (UNIX Cell Manager), or in the
<Data_Protector_home>\Config\server\integ\config\sap\
<client_name>%<ORACLE_SID> file (Windows Cell Manager).
2. On UNIX, it creates a soft link for backint from the directory in which SAP R/3 utilities are stored to /opt/omni/lbin (HP-UX and Solaris systems) or /usr/omni/bin (other UNIX systems).
3. On Windows, copies the backint program from the
<Data_Protector_home>\bin directory to the directory in which the SAP R/3 backup utilities reside.
Checking the SAP R/3 Configuration - Data Protector GUI
To check the configuration of your SAP R/3 Database Server, proceed as follows:
1. Right-click the SAP R/3 Database Server system.
2. Click Check Configuration.
If the configuration is successful, you should receive a message confirming that the integration was properly configured.
NOTE The target database must be online during the check.
The configuration can also be also checked if you have already created and saved a backup specification for a particular SAP R/3 Database Server. Proceed as follows:
1. In the Data Protector Manager, switch to the Backup context.
In the Scoping Pane, expand Backup, Backup Specification, then SAP R/3.
2. In the Results Area, double-click the backup specification, then select Properties.
3. In the Source property page, right-click the name of the SAP R/3 Database Server, then click Check Configuration.
Figure 2-9 Checking the SAP R/3 Configuration
You can also (re)configure an SAP R/3 Database Server by right-clicking it and selecting Configure.
Checking the SAP R/3 Configuration - Data Protector CLI
To check the SAP R/3 configuration, start the following command on the client:
util_sap.exe -CHKCONF <ORACLE_SID>.
Data Protector verifies the configuration by attempting to connect to the SAP R/3 Database Server using the information that was specified and saved during the configuration.
In case of an error, the error number is displayed in the form
*RETVAL*<error number>.
On UNIX, to get the error description, start the
/opt/omni/lbin/omnigetmsg 12 <error number> (HP-UX and Solaris systems) or /usr/omni/bin/omnigetmsg 12 <error number> (other UNIX systems) command.