backup_mode

This parameter is used by BRBACKUP to determine the scope of the backup activity.

Syntax: backup_mode = all|all_data|full|incr|<tablespace>|
<file_ID>|<file_ID1>-<file_ID2>|<generic_path>|sap_dir|
ora_dir|all_dir|<object_list>

Default: all

Possible values:

·        all: Whole database backup using BRBACKUP.

·        all_data: Save the files of all tablespaces which are not pure index tablespaces or empty.

·        full: Full database backup (level 0). See Incremental Backup.

·        incr: Incremental backup with RMAN. See Incremental Backup.

·        <tablespace>: The files of the specified tablespaces are backed up by BRBACKUP.

·        <file_ID>: The file with this file ID are backed up. For data files, this is the Oracle file ID. Control files can be addressed with the file ID 0. Online redo log files can be addressed using the file ID 0<n>, <n> is the redo log group number. Specify file ID 00 to back up all existing online redo log files. Temporary files are identified by negative numbers.

·        <file_ID1>-<file_ID2>: The files in this interval are backed up.

·        <generic_path>: By entering a full path, you can save database files, non-database files, or the specified directory. By entering a generic path, you can save database data files whose name starts with that path. In this case, the path must contain at least the SAPDATA_HOME directory and an additional generic specification (for example, sapdata<n>) in the path.

·        sap_dir: With this option, you can automatically determine and save all the files of the SAP environment. This means that the following directory trees are saved: /sapmnt/<SAPSID>, /usr/sap/<SAPSID>, /usr/sap/trans This option could, for example be used after an SAP upgrade. Saving with the sap_dir option should not replace regular backups of the file systems using operating system tools.

You can only use this option when saving to tape and when not performing a verification of the backup.

·        ora_dir: With this option, you can automatically determine and save all the non-database files of the Oracle environment. This means that the directory trees under <ORACLE_HOME> (except for the directories sapdata<n> and saplog- or origlog/mirrlog) are saved. You could, for example, use this option after an Oracle migration. Saving with the option ora_dir should not replace regular backups of the file systems with operating system tools.

You can only use this option when saving to tape and when not carrying out a verification of the backup.

·        all_dir: This option is a combination of sap_dir and ora_dir. It means the same as –m sap_dir,ora_dir.

·        <object list>: You can enter an object list, as described in Initialization Profile init<DBSID>.sap. This list can also include the key word all. However, we recommend processing database files and non-database files separately.

For UNIX systems: Start BRBACKUP to save the SAP or Oracle environment (backup_mode = sap_dir | ora_dir) under user root, as otherwise you will not have the authorizations required for the directory to be saved.

Saving and restoring under rootalso has the advantage that you can be sure that the settings for the user and authorizations for the files and directories will be kept after restoring.

The root user must have the environment of the corresponding ora<sid> user for BRBACKUP to be started successfully.