NetBackup™ Backup Planning and Performance Tuning Guide
- NetBackup capacity planning
- Primary server configuration guidelines- Size guidance for the NetBackup primary server and domain
- Factors that limit job scheduling
- More than one backup job per second
- Stagger the submission of jobs for better load distribution
- NetBackup job delays
- Selection of storage units: performance considerations
- About file system capacity and NetBackup performance
- About the primary server NetBackup catalog
- Guidelines for managing the primary server NetBackup catalog
- Adjusting the batch size for sending metadata to the NetBackup catalog
- Methods for managing the catalog size
- Performance guidelines for NetBackup policies
- Legacy error log fields
 
- Media server configuration guidelines- NetBackup hardware design and tuning considerations
- About NetBackup Media Server Deduplication (MSDP)- Data segmentation
- Fingerprint lookup for deduplication
- Predictive and sampling cache scheme
- Data store
- Space reclamation
- System resource usage and tuning considerations
- Memory considerations
- I/O considerations
- Network considerations
- CPU considerations
- OS tuning considerations
- MSDP tuning considerations
- MSDP sizing considerations
 
- Cloud tier sizing and performance
- Accelerator performance considerations
 
- Media configuration guidelines- About dedicated versus shared backup environments
- Suggestions for NetBackup media pools
- Disk versus tape: performance considerations
- NetBackup media not available
- About the threshold for media errors
- Adjusting the media_error_threshold
- About tape I/O error handling
- About NetBackup media manager tape drive selection
 
- How to identify performance bottlenecks
- Best practices- Best practices: NetBackup SAN Client
- Best practices: NetBackup AdvancedDisk
- Best practices: Disk pool configuration - setting concurrent jobs and maximum I/O streams
- Best practices: About disk staging and NetBackup performance
- Best practices: Supported tape drive technologies for NetBackup
- Best practices: NetBackup tape drive cleaning
- Best practices: NetBackup data recovery methods
- Best practices: Suggestions for disaster recovery planning
- Best practices: NetBackup naming conventions
- Best practices: NetBackup duplication
- Best practices: NetBackup deduplication
- Best practices: Universal shares
- NetBackup for VMware sizing and best practices
- Best practices: Storage lifecycle policies (SLPs)
- Best practices: NetBackup NAS-Data-Protection (D-NAS)
- Best practices: NetBackup for Nutanix AHV
- Best practices: NetBackup Sybase database
- Best practices: Avoiding media server resource bottlenecks with Oracle VLDB backups
- Best practices: Avoiding media server resource bottlenecks with MSDPLB+ prefix policy
- Best practices: Cloud deployment considerations
 
- Measuring Performance- Measuring NetBackup performance: overview
- How to control system variables for consistent testing conditions
- Running a performance test without interference from other jobs
- About evaluating NetBackup performance
- Evaluating NetBackup performance through the Activity Monitor
- Evaluating NetBackup performance through the All Log Entries report
- Table of NetBackup All Log Entries report
- Evaluating system components- About measuring performance independent of tape or disk output
- Measuring performance with bpbkar
- Bypassing disk performance with the SKIP_DISK_WRITES touch file
- Measuring performance with the GEN_DATA directive (Linux/UNIX)
- Monitoring Linux/UNIX CPU load
- Monitoring Linux/UNIX memory use
- Monitoring Linux/UNIX disk load
- Monitoring Linux/UNIX network traffic
- Monitoring Linux/Unix system resource usage with dstat
- About the Windows Performance Monitor
- Monitoring Windows CPU load
- Monitoring Windows memory use
- Monitoring Windows disk load
 
- Increasing disk performance
 
- Tuning the NetBackup data transfer path- About the NetBackup data transfer path
- About tuning the data transfer path
- Tuning suggestions for the NetBackup data transfer path
- NetBackup client performance in the 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)- Default number of shared data buffers
- Default size of shared data buffers
- Amount of shared memory required by NetBackup
- How to change the number of shared data buffers
- Notes on number data buffers files
- How to change the size of shared data buffers
- Notes on size data buffer files
- Size values for shared data buffers
- Note on shared memory and NetBackup for NDMP
- Recommended shared memory settings
- Recommended number of data buffers for SAN Client and FT media server
- Testing changes made to shared memory
 
- About NetBackup wait and delay counters
- Changing parent and child delay values for NetBackup
- About the communication between NetBackup client and media server- Processes used in NetBackup client-server communication
- Roles of processes during backup and restore
- Finding wait and delay counter values
- Note on log file creation
- About tunable parameters reported in the bptm log
- Example of using wait and delay counter values
- Issues uncovered by wait and delay counter values
 
- Estimating the effect of multiple copies on backup performance
- Effect of fragment size on NetBackup restores
- Other NetBackup restore performance issues
 
- About shared memory (number and size of data buffers)
- NetBackup storage device performance in the data transfer path
 
- Tuning other NetBackup components- When to use multiplexing and multiple data streams
- Effects of multiplexing and multistreaming on backup and restore
- How to improve NetBackup resource allocation
- Encryption and NetBackup performance
- Compression and NetBackup performance
- How to enable NetBackup compression
- Effect of encryption plus compression on NetBackup performance
- Information on NetBackup Java performance improvements
- Information on NetBackup Vault
- Fast recovery with Bare Metal Restore
- How to improve performance when backing up many small files
- How to improve FlashBackup performance
- Veritas NetBackup OpsCenter
 
- Tuning disk I/O performance
Notes on performance hierarchies
The hardware components between interconnection levels can also affect bandwidth, as follows:
- A drive has sequential access bandwidth and average latency times for seek and rotational delays. - Drives perform optimally when doing sequential I/O to disk. Non-sequential I/O forces movement of the disk head (that is, seek and rotational latency). This movement is a huge overhead compared to the amount of data transferred. The more non-sequential I/O done, the slower it becomes. - Simultaneously reading or writing more than one stream results in a mix of short bursts of sequential I/O with seek and rotational latency in between. This situation significantly degrades overall throughput, especially when the drive approaches 85% capacity. Different drive types have different seek and rotational latency specifications. Therefore, the type of drive has a large effect on the amount of degradation. - From best to worst, such disk drives are Serial Attach SCSI (SAS). "SATA" Serial ATA drives are rarely used for enterprise backup systems. SATA Solid-State Disks (SSDs) have access times at least twice that of their rotating disk counterparts and a 0.1 versus 12-millisecond access time. NVMe Gen4 SSDs have speeds of 3.8Gb/s writes and 7GB/s reads. For large repositories of data that is kept available, but if speed of retrieval is not a prime concern disk drive is the largest most cost efficient storage medium. 
- A RAID controller has cache memory of varying sizes. The controller also does the parity calculations for RAID-5 or RAID-6. RAID-5 can be used on SSD systems as the rebuild time is fast enough to not have a concurrent failure. RAID-6 or RAID-10 is required for Disk-based storage. 
- A PCIe card can be limited either by the speed of the ports or the clock rate to the PCIe slot. More information about the size and speed of the PCIe configurations is available: 
Memory can be a limit if there is intensive non-I/O activity in the system. Ensure that you follow the 1GB of memory to 1TB of MSDP storage so that the SHA-2 encryption is efficiently handled.
While CPU performance contributes to all performance, it is not the bottleneck in most modern systems for I/O intensive workloads. Very little work is done at that level. The CPU must execute a read operation and a write operation, but those operations do not take up much bandwidth. An exception fingerprint calculation in MSDP deduplication is CPU intensive. High number of concurrent streams with a high deduplication ratio can create a CPU bottleneck. Plan for at least one CPU thread per backup stream on lower powered systems. Up to four concurrent streams per core (two threads per core) on Intel processors are possible with small and numerous file backups