Runtimes are much longer than normal when you save.
Cause 1.
----------
There is a high CPU load, possibly due to looping processes. This has a negative effect in particular if you use software compression (compress = yes in init
Cause 2.
----------
The dd ouput on tape is not blocked when you save to a remote host.
AIX only: The SMIT setting for "tape block size" is not equal to 0.
The "cpio_flags" do not define a block for the cpio output.
Cause 3.
----------
The cpio performance is poor on Windows NT.
Solution 1.
---------
Check the CPU load: using process lists (command ps), for example. Identify processes that have used more than 1,000 CPU seconds. If these are looping processes (for example, the CPU load grows quickly), kill them or boot the host.
Solution 2.
---------
Include the option bs=5k in init
copy_in_cmd = "dd bs=64k if=$"
copy_out_cmd = "dd bs=64k of=$"
You can also use block sizes other than 64k.
AIX only: Set the SMIT setting for "tape block size" to 0 (variable block size).
The init
If this burdens the operating system, you can work with larger blocking factors and therefore achieve shorter save times.
Solution 3.
---------
As of BRBACKUP 3.1, you can use the dd command for backups of the database files along with the cpio. This can improve the performance. For more information, see Note 71058.
If this does not solve the problem, your only solution is to change the backup method:
3.1. Using the SAP backup library with RMAN. To do this, change the following init
and activate the SAP backup library (Note 142635).
3.2. Use an external backup tool through the BACKINT interface:
backup_dev_type = util_file | util_file_online
You can find information about partners who support this interface in Note 83792.
Keyword: BRBACKUP
No comments:
Post a Comment