NetBackup™ Backup Planning and Performance Tuning Guide
- NetBackup capacity planning
- Primary server configuration guidelines
- Media server configuration guidelines
- NetBackup hardware design and tuning considerations
- About NetBackup Media Server Deduplication (MSDP)
- MSDP tuning considerations
- MSDP sizing considerations
- Accelerator performance considerations
- Media configuration guidelines
- How to identify performance bottlenecks
- Best practices
- Best practices: NetBackup AdvancedDisk
- Best practices: NetBackup tape drive cleaning
- Best practices: Universal shares
- NetBackup for VMware sizing and best practices
- Best practices: Storage lifecycle policies (SLPs)
- Measuring Performance
- Table of NetBackup All Log Entries report
- Evaluating system components
- Tuning the NetBackup data transfer path
- NetBackup network performance in the data transfer path
- NetBackup server performance in the data transfer path
- About shared memory (number and size of data buffers)
- About the communication between NetBackup client and media server
- Effect of fragment size on NetBackup restores
- Other NetBackup restore performance issues
- About shared memory (number and size of data buffers)
- Tuning other NetBackup components
- How to improve NetBackup resource allocation
- How to improve FlashBackup performance
- Tuning disk I/O performance
Additional information on the NetBackup All Log Entries report
For other NetBackup operations, the NetBackup All Log Entries report has entries that are similar to those in the following table:
See Table: Messages in All Log Entries report.
For example, it has entries for image duplication operations that create additional copies of a backup image. The entries may be useful for analyzing the performance of NetBackup.
The bptm debug log file for tape backups (or bpdm log file for disk backups) contains the entries that are in the All Log Entries report. The log also has additional detail about the operation that may be useful. One example is the message on intermediate data throughput rate for multiplexed backups:
... intermediate after number successful, number Kbytes at number Kbytes/sec
This message is generated whenever an individual backup job completes that is part of a multiplexed backup group. For example, the debug log file for a multiplexed backup group (that consists of three individual backup jobs) may include the following: two intermediate status lines, then the final (overall) throughput rate.
For a backup operation, the bpbkar debug log file also contains additional detail about the operation that may be useful.
Note that writing the debug log files during the NetBackup operation introduces overhead that may not be present in a production environment. Factor that additional overhead into your calculations.
The information in the All Logs report is also found in the following locations:
Linux/UNIX
/usr/openv/netbackup/db/error
Windows
install_path\NetBackup\db\error
See the NetBackup Logging Reference Guideto learn how to set up NetBackup to write these debug log files.