Component : Database Administration with Oracle -

Solution : https://service.sap.com/sap/support/notes/13994 (SAP Service marketplace login required)

Summary :
The SAP Note outlines the prolonged runtimes observed in the BRBACKUP process. Three primary causes are identified. Cause 1 relates to high CPU load due to looping processes, negatively impacting systems using software compression. Cause 2 concerns the lack of blocking in dd output during remote host saves, with specific AIX settings for tape block size. Cause 3 attributes delay to poor cpio performance on Windows NT. For resolution, monitoring and managing CPU load through process lists, optimizing parameter settings in init.sap, and using the dd command or alternative backup methods, including SAP backup library with RMAN or external tools via BACKINT, are recommended.

Key words :
achieve shorter save times, cpu load grows quickly, high cpu load, option bs=5k, larger blocking factors, tape_copy_cmd = rmanand activate, tape block size, variable block size, external backup tool, sap backup library

Related Notes :

71058	Innovations in BRBACKUP and BRARCHIVE Version 3.1G
27937	BR278E ... Data Dictionary: write error: Invalid argument
13372	BRBACKUP reaches end of tape