HP OpenView Storage B6960-96008 SAP R/3 Specific Backup Options, Logs?, Log file, BR Backup, 186

Integrating SAP R/3 and Data Protector

Configuring an SAP R/3 Backup

NOTE	The parallelism of a backup (the number of streams your SAP R/3
	database is backed up with) is set automatically. If load balancing is
	used, the parallelism represents the sum of the device concurrencies
	defined in the SAP R/3 backup specification. For more information on
	load balancing, see the online Help index “load balancing”.

The database system of an SAP R/3 system must operate in the ARCHIVELOG mode. This prevents the overwriting of online redo log files that have not yet been saved. To protect the archived directory from overflowing, empty the directory regularly.

Why Archive Redo The reasons for archiving redo log files are listed below:

Logs?

•In the event of a failure, consistent database status can only be recovered if all the relevant redo log files are available.

•An online backup of data files is useless if the related redo log files are missing. It is therefore necessary to archive the redo log files generated during the online backup immediately after running

BRBACKUP.

SAP R/3 Specific Backup Options

The SAP R/3 specific backup options are specified using the Data Protector GUI in the Application Specific Options window. The window can be accessed from the Options property page of an SAP R/3 backup specification by clicking the Advanced tab.

Log file	Specifies the pathname of the backint
	log file. By default, this log file is not
	generated, as Data Protector stores
	all relevant information about
	backup sessions in the database.
	However, the user may decide to
	enable local logging by specifying a
	log file pathname.
BR Backup	Enter the BRBACKUP command
	options. See the SAP R/3 Online
	Documentation for information about

186 Chapter 2