Unattended Backup 

Under certain conditions you can make a backup without monitoring or operator intervention. Note that the details are highly specific to the operating system.

Note the operating system-specific options for scheduling background jobs.
See also, for example, BRBACKUP/BRARCHIVE with tips for Windows NT.

Parallel backup

You can make unattended backups if you have enough backup devices. This means that you need <n> backup devices if <n> volumes (for example, tapes) are required for the backup. BRBACKUP can then back up to these devices in parallel, without the operator having to change the volumes.
 Parallel Backup

Backup with Automatic Tape Changers

If you want to use autochangers, you need to define the rewind_offline parameter appropriately and set backup_dev_type to tape_auto or pipe_auto .
Automatic Tape Changing

Serial Backup

Unattended backup is also possible if fewer parallel copy processes than connected backup devices are available. To do this, change the parameter exec_parallel. If you need several volumes for a backup, the backup devices are not used in parallel. In this case they are used in accordance with the number of copy processes set.

In order to be able to make a parallel or serial backup on several tape devices, the addresses of the backup devices must be defined in the init<DBSID>.sap parameters tape_address and tape_address_rewind (or backup_root_dir in the case of a disk backup).

tape_address = (dev/rmt/0mn, /dev/rmt/1mn)
tape_address_rew = (dev/rmt/0m, /dev/rmt/1m)

BRBACKUP/BRARCHIVE Backups in One Run

The complete backup of the database files and the offline redo log files can be executed with a single start of BRBACKUP (command option -a|-archive).
 BRBACKUP and BRARCHIVE Backups in One Run

Backup with CRON

For a successful unattended backup using CRON, the following requirements must be met:

If automatic tape management is active, first determine the tape names by entering the commands brbackup|brarchive -q .

Use brbackup|brarchive -q check to verify that the required volumes were actually mounted.

If automatic tape management is not active, mount tapes whose expiration period has expired.

Online backup of the complete database
unattended operation
daily Monday through Friday
backup to be started at 10.00 p.m.

#Min(0-59) Hrs (0-23) Day (1-31) Mon(1-12) WD (0-Sun,...,6-Sat)

00 22 * * 1-5

su - ora<sapsid> -c "brbackup -t online -c force -u"%system/<password>

or under <sid>adm:

su - <sapsid>adm -c "brbackup -t online -c force -u /"

Offline backup of the complete database
unattended operation
daily Monday through Friday
backup to be started at 10.00 p.m
R/3 System shut down

#Min(0-59) Hrs (0-23) Day (1-31) Mon(1-12) WD (0-Sun,...,6-Sat)

00 22 * * 1-5

/backup1.sh

The script backup1.sh in the root directory could have the following content:

su - <sapsid>adm -c "stopsap R3"

su - ora<sapsid> -c "brbackup -t offline -c force -u" <<END

system/<password>

END

su - <sapsid>adm -c startsap

Offline backup of the complete database
unattended operation
daily; Monday through Friday
backup to be started at 10.00 p.m
R/3 System shut down

#Min(0-59) Hrs (0-23) Day (1-31) Mon(1-12) WD (0-Sun,...,6-Sat)

00 22 * * 1-5

/backup2.sh

The script backup2.sh in the root directory could have the following content:

su - ora<sapsid> -c "brbackup -t offline_force -c force -u" <<END

system/<password>

END

su - <sapsid>adm -c "saplicense -check"

Archiving the offline redo log files
unattended operation
daily; Monday through Friday
backup to be started at 8.00 a.m.
parallel archiving to two backup devices.

#Min(0-59) Hrs (0-23) Day (1-31) Mon(1-12) WD (0-Sun,...,6-Sat)

00 8 * * 1-5

su - ora<sapsid> -c "brarchive -ssd -c force -u"%system/<password>