Verifying the Data Protection for SAP setup

Edit online

When you are troubleshooting issues while using Data Protection for SAP software there are items that you can check to ensure that the setup completed correctly.

Review these considerations to better understand the installation setup on UNIX™ or Linux™ systems:

Make sure an entry similar to this example is defined in the /etc/inittab file:
```
po64:2:respawn:/usr/tivoli/tsm/tdp_r3/ora64/prole -p tdpr3ora64 
Server component hostname 5126
```
```
po64:2:respawn:/usr/tivoli/tsm/tdp_r3/ora64/prole -p tdpr3ora64 
Server component hostname 5126
```
```
pd64:2:respawn:/usr/tivoli/tsm/tdp_r3/db264/prole -p tdpr3db264 
Server component hostname 5126
```
```
pd64:2:respawn:/usr/tivoli/tsm/tdp_r3/db264/prole 
-p tdpr3db264 Server component hostname 5126
```
This entry starts a daemon process for ProLE. This process listens on the following ports:
- Data Protection for SAP port tdpr3ora64 for backint.
- RMAN connections for Oracle 64-bit port tdpr3ora64 for backint, RMAN connections, and Data Protection for SAP.
The port can have a different name; however, the name must match the name in the /etc/services file as shown in this example:
```
tdpr3ora64      57323/tcp
```
The lines are added to the /etc/services file during the installation process.
Make sure the Data Protection for SAP configuration file initSID.utl is in the $ORACLE_HOME/dbs directory.
When you use the BR*Tools with Data Protection for SAP, modify the initSID.sap file by setting backup_dev_type = util_file and variable util_par_file to the fully qualified path and file name of initSID.utl.

Review these considerations to better understand the installation setup on Windows™ systems:

Make sure that all files are installed.
Verify that service ProLE Service is running and set to automatic startup. If this service is not running, Data Protection for SAP does not function properly.
The installer adds lines to the %SYSTEMROOT%\system32\drivers\etc\services file similar to the example:
(Data Protection for SAP for DB2)
```
tdpr3db264      57324/tcp
```
The example shows the Data Protection for SAP 64-bit port.
(Data Protection for SAP for Oracle)
```
tdpr3ora64      57323/tcp
```
The example shows the Data Protection for SAP 64-bit port. For Data Protection for SAP for Oracle, this port name is needed for the initSID.sap file when RMAN is configured.
Make sure the Data Protection for SAP configuration file initSID.utl is in the %ORACLE_HOME%\database directoryin the directory pointed to by the TDP_DIR environment variable.
Make sure the Data Protection for SAP configuration file initSID.utl is in the directory pointed to by the TDP_DIR environment variable (on DB2®).
Make sure the Data Protection for SAP configuration file initSID.utl is in the %ORACLE_HOME%\database directory (on Oracle).
When you use the BR*Tools, modify the initSID.sap file by setting backup_dev_type = util_file and variable util_par_file to the fully qualified path and file name of initSID.utl.
The vendor environment file vendor.env must contain the fully qualified path and file name of the initSID.utl file for Data Protection for SAP for DB2.
The vendor environment file vendor.env is to contain the path of the location where the Data Protection for SAP for DB2 runs logs that are written. If this location is not specified, a temporary directory of the system is used.
The names of the IBM Storage Protect™ servers that are specified in initSID.utl must match the names in the dsm.sys file. If the IBM Storage Protect API or IBM Storage Protect backup archive client are installed into their default locations, then it is not necessary to set the DSMI_* variables. If the variables are set, however, make sure that they specify the correct directories and files. The user ID that runs the backups must have the correct permissions to access all of files and directories that are specified by these variables.
Also, verify that write permissions exist for the initSID.bki file as this file is the only one to which Data Protection for SAP writes persistent information.

This graphic depicts the interrelationships of the SAP and configuration files on UNIX or Linux. — Figure 1. SAP and Data Protection for SAP for Oracle configuration files on UNIX or Linux

On UNIX or Linux systems, the names of the IBM Storage Protect servers that are specified in initSID.utl must match the names in the dsm.sys file. If the IBM Storage Protect API or IBM Storage Protect backup archive client are installed into their default locations, then it is not necessary to set the DSMI_* variables. If the variables are set, however, make sure that they specify the correct directories and files. The user ID that runs the backups must have the correct permissions to access all of files and directories that are specified by these variables. Also, verify that write permissions exist for the initSID.bki file as this file is the only one to which Data Protection for SAP writes persistent information.

On Windows systems, the dsm.opt file is used instead of the dsm.sys file. However, the content of this file is not relevant to Data Protection for SAP. The directory that contains the dsm.opt file must also contain a server.opt file for each server that is specified in the initSID.utl file. The environment variable DSMI_CONFIG must specify an option file within this directory. DSMI_CONFIG is to specify the dsm.opt file in this directory. The DSMI_DIR environment variable must also specify the directory where the IBM Storage Protect API message text file is in. This example shows a typical the c:\Program Files\Tivoli\tsm\api64 directory.