Please enter search query.
Search <book_title>...
NetBackup™ Backup Planning and Performance Tuning Guide
Last Published:
2024-04-16
Product(s):
NetBackup & Alta Data Protection (10.4, 10.3.0.1, 10.3, 10.2.0.1, 10.2, 10.1.1, 10.1, 10.0.0.1, 10.0, 9.1.0.1, 9.1, 9.0.0.1, 9.0, 8.3.0.2, 8.3.0.1, 8.3)
- 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
More than one backup job per second
Starting from NetBackup 8.2, NetBackup removed the one backup job per second limitation within a primary server. With the change, the limit of starting only one job per second still holds for a single client, however, multiple jobs from different clients may be started within a second. NetBackup can scale to higher job counts with appropriate hardware resources.
Multiple backup jobs from multiple clients all starting at the same time may cause a temporary CPU and memory usage surge, sometimes significantly. The overall performance effect maybe marginal, however, if primary server is already CPU-bound or memory-bound, this temporary surge can cause the system to become unresponsive.