BRBACKUP calls cpio in order to copy individual files from the hard disk to tape. As a result, throughput is basically determined by cpio .

BRBACKUP offers a number of functions to enable an optimal backup of large databases.

• BRBACKUP can backup in parallel to several locally mounted tape units.

• All files to be saved are distributed to the volumes (tapes) inserted in the tape units. BRBACKUP has different optimization targets (see Optimization of File Distribution).

• As the database server is working at 100% during the backup, other activities on the computer should be reduced to the absolute minimum during the backup. Virtually all of the computer's resources should be available for the backup.

• No cpio continuation mechanism is supported during parallel backups (see cpio Continuation Tape), that is, individual files must always be completely saved onto one volume. Tape swapping must always be carried out by BRBACKUP. Therefore, the size of a file to be saved must not exceed the tape capacity. If you work with tape units with hardware compression, the size of the compressed file must not exceed the tape capacity. Make sure that the tape capacity is not set too high, in order to avoid reaching the end of the tape.

• Since individual files can only be written in their entirety to a volume, there is a certain amount of wastage when distributing the files to the available tapes. That is, the tape capacity cannot be fully used. When distributing the files, BRBACKUP makes sure that the tape capacity is never exceeded. The size of the tape header files (label, init<DBSID>.ora , init<DBSID>.sap ) and the log files at the end of the tape (central, detailed and summary log) are not taken into account.