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
Measuring performance with bpbkar
Use this procedure to measure disk performance with bpbkar.
To measure disk I/O using the bpbkar command
- Set the logging level to 1.
Enter the following:
Linux/UNIX:
/usr/openv/netbackup/bin/bpbkar -nocont -dt 0 -nofileinfo -nokeepalives file system > /dev/null
Where file system is the path being backed up.
Windows:
install_path\NetBackup\bin\bpbkar32 -nocont X:\ > NUL
Where X:\ is the path being backed up.
Check how long it took NetBackup to move the data from the client disk:
Linux/UNIX:
The start time is shown in the bpbkar initialize entry in the
bpbkar
log. The end time is shown in the entry bpbkar main: INF - Client completed sending data for backup. The elapse time is the time duration between the start time and the end time.The start time is the first PrintFile entry in the
bpbkar
log. The end time is the entry "Client completed sending data for backup." The amount of data is given in the entry "Total Size."Windows:
Check the
bpbkar
log for the entry "Elapsed time". For example:Elapsed time: 1622 secs 59370573 bps