(C)SEP AG

Copyright 1999-2011 by SEP AG. All Rights reserved.

Any form of reproduction of the contents or parts of this manual is allowed only with the express written permission from SEP AG. When compiling and designing user documentation SEP AG uses great diligence and attempts to deliver accurate and correct information. However, SEP AG cannot issue a guarantee for the contents of this manual.

Installation of the SEP sesam SAP R/3 Oracle Module

Prerequisites

1. Installed Database SAP/R3 ORACLE DB at least Version 7.x with full functionality

2. These Environment variables must be set for the SAP/R3 ORACLE DB:

• ORACLE_SID
• ORACLE_HOME
• SAPDATA_HOME

Installation on the SAP R/3 Server in UNIX

1. The regular SEP sesam Client for UNIX has to be installed on the SAP R/3 server.

2. Unpack the tar-archive into a temporary directory. The archive contains these files:

• backint
• init.utl

3. Copy the file backint into ORACLE program files folder /usr/sap/<ORACLE SID>/SYS/exe/run. If there already is a \backint\ rename it first. This File has to be executable for the Oracle SAP R/3 User.

4. Check if the program sbc_com_interface is executable for the ORACLE user in the directory <SESAM DIR>/bin/sesam.

5. The file init.utl has to be copied to $ORACLE HOME/dbs/init<ORACLE SID>.utl for the ORACLE DB

Installation on the SAP R/3 Server in Windows

1. The normal SEP sesam backup client for Windows has to be installed on the SAP R/3 Server

2. Unpack the zip-archive into a temporary folder. The archive contains the following files:

• backint.exe
• init.utl

3. Copy the file backint.exe into the respective program directory. For ORACLE this is <SAP MNT>/%ORACLE SID%/SYS/exe/run. If there already is a \backint\ rename it first.

4. The file init.utl must be copied to %ORACLE_HOME%\databases\init%ORACLE SID%.utl and the directory %ORACLE_HOME%\saptrace i.e. %SAPDATA_HOME%\saptrace has to be created.

Configuration on the SEP sesam Server

The SAP R/3 server has to be added as a client on the SEP sesam Server. Additionally, at least one task with the backup type SAP R/3 has to be created for the SAP R/3 server. You can also configure more tasks e.g. to distinguish database backups from archivelog backups. The entry for source can be chosen freely. What data is actually backed up only depends on the respective SAP R/3 backup call. This task can't be used for regular backups.

Configuration on the SEP sesam SAP/R3 Oracle client

In order for SAP R/3 to use the backint gateway the following entries have to be changed in the SAP profile file init<ORACLE_SID> in the case of ORACLE.

• backup_dev_type= util_file #configure Backup Device Type
• util_par_file= $ORACLE HOME/dbs/init<ORACLE SID>.utl

Several SAP R/3 profiles can be created and used for backup/restore. Again, various util_par_file parameters can be set for them. With this you can, for example, use different SEP sesam drives for different backup types. At least the following entries have to be set in the util_par_file (e.g. $ORACLE HOME/dbs/ini<ORACLE SID>.utl):

• SESAM_SERVER=<SEP sesam Server> Name of the SEP sesam Server you want to back up on.
• SESAM_JOB=<Sesam SAP Client Task> The name of the already configured backup task.
• SESAM_DRIVE=<Sesam Drive Number> Number of the drive that you want to back up on.
• SESAM_POOL=<Sesam Mediapool> Name of the SEP sesam media pool that you want to back up on.

Further optional configuration-parameters:

• SBC=<SESAM_PATH> Full path of the SEP sesam backup program. Only has to be set if the standard sbc is being used.
• PORT=<Sesam_Server_Communication_Port> only necessary if the STPD port was changed during the installation of the SEP sesam server.
• SESAM_TAPESERVER=<Tapeserver> IP-Name of the tapeserver that you want to back up on. The backup net that you want to use can be chosen with this entry.

Log Files SAP R/3 on ORACLE

The following log files are written by the individual SEP sesam SAP R/3 backup modules in $ORACLE HOME/saptrace i.e. $SAPDATA HOME/saptrace:

BACKINT

Name: backint <ORACLE_SID>.log

Max. Log Levels: 3 (ERROR, WARNING, INFO)

Description: Message if the backint program

SBC

Name: sbc <ORACLE_SID>.log

Max. Log Levels: 6

Description: Messages of the SEP sesam backup client

init<ORACLE_SID>.utl: SBC TRACE LEVEL (default: 2)

SBC_COM_INTERFACE

Name: sbc_com_<ORACLE_SID>.log

Max. Log Levels: 3 (ERROR, WARNING, INFO)

Description: Logging of the sbc_com_interface program

init<ORACLE_SID>.utl: SBC_COM_TRACE_LEVEL (default: 0)

BR* Tools Calls for SAP/R3 on ORACLE DB

BRBACKUP

1. brbackup -d util file -t offline -m all [-u internal/passwd] [-c]

-> complete offline backup

2. brbackup -d util file online -t online -m all [-u internal/passwd] [-c]

-> complete online backup

3. brbackup d util file -t offline -m PSAPSTABI,PSAPPOOLD[,TBLSP3, ...]

-> partial offline backup

4. brbackup d util file -t online -m PSAPSTABI,PSAPPOOLD[,TBLSP3, ..]

-> partial online backup

5. brbackup d util file online -t online -m PSAPSTABI,PSAPPOOLD[,TBLSP3, ..]

-> partial online backup with a dynamic BEGIN/END BACKUP switch

BRARCHIVE

1. brarchive -d util file -s

-> Backup offline redo Log-Files

2. brarchive -d util file -cd

-> Copy and delete the backed up offline redo log files and back up the new redo logs

BRRESTORE

1. brrestore -d util file -b last -m full

-> full restore of the offline backup a after full offline backup

2. brrestore -d util file -b last -m all

-> full restore of the redo log full online backup after a full online backup (with dynamic switch)

3. brrestore d util file -b <part offline back log> -m PSAPSTABI=<restore directory>

-> partial restore of the partial offline backup into a different restore rirectory

4. brrestore -d util file -a <log nr2>-<log nr5>=<restore directory>

-> restore of the offline redo Log-Files written between the partial offline and partial online backup

NAS/SAN extension for ORACLE

For backups in NAS/SAN environments SEP AG provides the possibility to store the data to a directly connected NAS/SAN device. That means the data communication work on the database server and the data transfer works on a dedicated server on which the data stand by in a identical way. The backup related load (network resp. cpu) will be displaced to the dedicated server. For this kind of backup a special license is necessary. In the file util_par_file (e.g. $ORACLE_HOME/dbs/ini<ORACLE_SID>.utl) the additional entry SESAM_REMOTE_CLIENT has to be configured:

SESAM_REMOTE_CLIENT=<Remote Client>

Name of the client where from the identical NAS/SAN data will be backed up.