Important Update: Cohesity Products Documentation
All Cohesity product documentation are now managed via the Cohesity Docs Portal: https://docs.cohesity.com/HomePage/Content/home.htm. Some documentation available here may not reflect the latest information or may no longer be accessible.
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: Malware scanning
- Understand malware scanning in NetBackup
- Enable malware scanning for all critical backup jobs
- Ensure antivirus software compatibility
- Test scanning configurations regularly
- Monitor and adjust based on backup job performance
- Ensure malware scanning is part of the restore process
- Maintain a security awareness program
- Leverage IRE for malware scanning
- Sizing for malware scanning of MSDP backup image
- Malware scan performance issue analysis
- 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
- Best practices: Calculate file hash
- 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
Sizing for malware scanning of MSDP backup image
This section outlines the methodology for sizing malware scan hosts when performing scans on backup images stored in MSDP storage. Proper sizing depends on several factors, including the nature and composition of the protected data, as well as the available spare IOPS capacity on the storage server where backup resides. The guidance provided here serves as a foundational framework for basic sizing considerations. For environment-specific sizing recommendations and advanced tuning, consult your Veritas account team or authorized reseller.
Key sizing parameters
Effective sizing for malware scan hosts requires answering several key questions related to the backup environment:
What type of data is being scanned? File types such as ZIP, image, or other archive formats require additional processing time, as contents must be extracted and individually scanned.
What is the volume and structure of the data? Understanding the total data size and the number of files per backup image is critical, as high file counts can significantly impact scan performance.
Where does the backup data reside? Identifying the specific storage server(s) used for scanning is essential.
Are multiple copies of the backup stored across different storage servers? This can influence scan strategy and scan host sizing.
What is the current load on the storage server? It's important to assess how many parallel scans the storage server can support to determine how many scan hosts are required.
The following formula can be used:
Number of scan hosts required = parallel scans limit set on storage server / optimal parallelization per scan host
As the number of parallel scans on a scan host increases, throughput improves. However, the percentage gain diminishes with each additional scan. Optimal parallelization is achieved at the point where the maximum number of parallel scans yields the highest throughput in terms of files scanned per hour.
Based on in-house testing, optimal parallelization per scan host is determined as follows:
Linux scan host with NFS share type can support upto 6 parallel scans
Windows scan host NFS/SMB share type can support upto 3 parallel scans
For example: If a storage server can support a maximum of 20 parallel scans at its current load, then:
Number of Linux scan hosts required = 20/6 ~ 4. Hence, 4 Linux scan hosts would suffice.
Number of Windows scan hosts required = 20/3 ~ 7. Hence, 7 Windows scan hosts would suffice
To estimate the scan duration for a given number of files, measure the scanning throughput using the current deployment. Trigger the maximum number of parallel scans configured per storage server to determine the effective throughput, expressed as the number of files scanned per hour.
The following formula can be used:
Expected time to scan (in hours) = (Number of backups * Average number of files in backup) / Throughput per hour.
For example: For a Linux scan host using NetBackup Malware Scanner and NFS share type
If throughput per hour = 12 million files per hour
Number of backups to scan = 100
Average number of files per backup = 500k
Expected time to scan (in hours) = (100 x 500,000 / 12,000,000) ~ 4 hours
In-house testing shows
Linux scan host using NetBackup Malware Scanner and NFS share type provides 4 times throughput compared to Windows scan host using NetBackup Malware scanner and NFS share type.
Throughput numbers for Standard/MS-Windows policy backup scans are 10 times more than VMWare VM backup scans. This difference can be attributed to the use of additional virtualization layer to mount virtual disk - while creating instant access of VM backup.