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
Summary of performance hierarchies
When you are putting together systems, remember that you are doing this to ensure that your data is available and has enough bandwidth/speed to meet the performance requirements. For this reason, invest in quality disk or SSD storage as criteria 1.
Next, configure enough bandwidth on your network to handle the peak amount of traffic allowing you to process the maximum concurrent jobs defined in the service level agreement.
Lastly, configure enough processor cores that are needed for the type of data to be backed up. Do not under populate the amount of DRAM allocated to the compute node. For example, we recommend at least 1GB of DRAM for every TB of storage for running deduplication.
More recommendations on the hardware design of the NetBackup compute node is available: