Integrating SAP R/3 and Data Protector

Configuring an SAP R/3 Backup

 

Each tablespace is switched into

 

backup mode just before the

 

backup and is switched out from

 

backup mode immediately after

 

the backup. As a result, the

 

increase in archived log files is

 

smaller compared to the backup

 

with the util_file device type.

 

However, if the database consists

 

of a large number of small files,

 

the backup can take longer.

Brbackup_RMAN_Offline

Backs up the shut-down database

 

using Oracle RMAN.

Brbackup_RMAN_Online

Backs up the active database. The

 

tablespace is locked for the time of

 

the whole backup using Oracle

 

RMAN.

Click OK.

 

4.In the Results Area, provide the following information:

In the Client drop-down list, select the SAP R/3 Database server that you want to back up. If the application is cluster-aware, select the virtual server of the SAP R/3 resource group (on Windows) or package (on UNIX).

In the Application database drop-down list, select the name of the Oracle Server instance (ORACLE_SID) on which the SAP R/3 Database Server is running.

On UNIX, enter also the SAP R/3 user name and its group name as described in “Configuring an SAP R/3 User in Data Protector (UNIX Systems Only)” on page 165.

Click Next.

5.If the SAP R/3 Database Server is already configured, the Source dialog box is displayed. Otherwise, you are prompted to configure it. See “Configuring an SAP R/3 Database Server” on page 167 for details.

6.In the Source property page, select the database objects you want to back up. Database objects include archive logs, tablespaces, and data files.

Chapter 2

181