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
Limiting the number of SLP secondary operations to maximize performance
Less is more. Run fewer jobs but allow each job to manage as much data as possible. SLP parameters can be used to assist the lifecycle to run duplication jobs more efficiently. To prevent the lifecycle from running numerous small duplication jobs in frequent succession, NetBackup accumulates lists of similar images into a batch. Then, each batch of images is copied as a set in one duplication job, instead of one image at a time. The NetBackup administrator can change how large the batch file scan becomes, or how frequently batch jobs are requested.
More information is available in the following technical articles:
Storage Lifecycle Policy (SLP) tuneable parameters to optimize the duplication process
Storage Lifecycle Policy (SLP) Cheat Sheet
Also see SLP Parameters properties in the NetBackup Administrator's Guide, Volume I
Table: Common SLP parameters that impact BID files
| SLP property | Default value |
|---|---|
Maximum size per duplication job The largest batch size that can run as a single duplication job. | 100 GB |
Minimum size per duplication job The smallest batch size that can run as a single duplication job. The job does not run until enough images accumulate to reach this minimum batch size or until the Force interval for small jobs time is reached. | 8 GB |
Maximum size per A.I.R. replication job The largest batch size that can run as a single job for Auto Image Replication. | 100 GB |
Maximum Images per A.I.R. Import job The largest number of images in a single batch that can run as an Auto Image Replication import job. | 250 |
Minimum Images per A.I.R. Import job The fewest number of images in a single batch that can run as an Auto Image Replication import job. The job does not run until either the minimum size is reached or the Force interval for small jobs time is reached. | 1 |
Force interval for small job The age that the oldest image in a batch must reach after which the batch is submitted as a duplication job. This value prevents many small duplication jobs from running at one time or running too frequently. It also prevents NetBackup from waiting too long before it submits a small job. | 30 minutes |
Effects of increasing these SLP parameters:
Minimum size per duplication job and Force interval for small job
Increasing the Minimum size per duplication job will cause the total number of images in a BID file to reach a higher size threshold before a small job will be started. The small job will be started after the Force interval for small job value is reached. This can have the effect of duplication jobs starting further apart because it will take more time for a total batch size to reach the limit.
Maximum size per duplication job
Increasing the Maximum size per duplication job will cause the maximum batch size for a single duplication job be raised to the specified size. A higher value can have the effect of reducing the number of duplication jobs that can run.
Maximum size per A.I.R. replication job
Increasing the Maximum size per A.I.R. replication job will cause the maximum batch size for a single A.I.R. replication job be raised to the specified size. A higher value can have the effect of reducing the number of A.I.R. replication jobs that run while managing more images at one time.
Maximum Images per A.I.R. Import job
Increasing the Maximum Images per A.I.R. Import job will cause the maximum number of images in a single job in an A.I.R. Import. A higher value can have the effect of reducing the number of A.I.R. Import jobs that run, while managing more images per job.
Minimum Images per A.I.R. Import job
Increasing the Minimum Images per A.I.R. Import job will cause the minimum number of images in a single job be increased and then wait until the Force interval for small job is reached. The effect of increasing this value is that fewer A.I.R. Import jobs run, but more images be managed with each job.