• online : Database backup in online mode, in other words, with the database running.
• online_cons : Database backup in online mode. As well as the database files, the offline redo log files generated during the backup are copied to the same volume. You then have a logically consistent dataset available. This backup of the offline redo log files with BRBACKUP runs completely independently of other BRARCHIVE backups.
• offline : Database backup in offline mode, in other words, the database is shut down during backup. When you select this parameter, BRBACKUP checks that no SAP system users are connected to the database. If an SAP System is active, the database is not shut down and BRBACKUP terminates the process with an error message (message number BR068E).
• offline_force : Database backup in offline mode, in other words, the database is shut down during backup. BRBACKUP always shuts down the database, even if the SAP System is active.
• offline_standby : Data backup of a standby database in offline mode; in other words, the standby database is shut down during the backup. This backup mode is only relevant for the disaster recovery configuration. See Standby Database Scenario.
• online_split : The mirror disks are split and backed up while the database is running. The tablespaces to be backed up are only placed in BACKUP status during the split. This backup mode is only relevant for the ‘split mirror’ configuration. See: Split Mirror Disks Backup.
• offline_split : The database is only shut down for the mirror disks split. The backup of the mirror disks can take place whilst the database is running. The R/3 System is available during the entire split mirror backup. Restriction: No transactions can be carried out during the short period of time that the database is shut down.
  This backup mode is only relevant for the ‘split mirror’ configuration. See: Split Mirror Disks Backup.
• offline_stop: Database backup in offline mode without a consequent startup of the database. After its backup the database can be transferred directly into the mount standby status.
  This type of backup is only relevant in the following case: The productive database is saved and then takes over the role of a standby database. The backup itself becomes a productive system. See: Standby Database Scenario:

Backup Mode.