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
Discovery
Discovery is the first step when a VMware Intelligent Policy (VIP) is used. This step is applicable only when automatic selection of virtual machines for backup via a VIP is enabled. It discovers virtual machines and filters them using the selection query specified in the policy. The resulting list determines which virtual machines are backed up.
To determine which virtual machines need to be protected, data for all virtual machines for each virtual server (vCenter / ESX) is fetched and evaluated. This is usually a fast operation. Data, once queried, is cached on the discovery host and reused. Typically, data that has been fetched within one hour is reused, but there are circumstances in which new data is fetched. You can control which discovery host is used for each policy; this can have a significant impact on backup and virtual infrastructure.
Consolidated discovery hosts
In some cases, it might be beneficial to use a fewer number of discovery hosts across policies. Each discovery host will query for all possible virtual machines from every configured virtual machine server by reusing discovery hosts from another policy. Subsequent policies can benefit from the cache built from a previous discovery. Reducing the number of times discovery is done can also reduce the load on the virtual infrastructure. This is especially a problem if various policies with multiple storage units (media servers) share the same backup window.
Consolidated policies
Policies are useful to help organize backup lifecycle and provide multiple levels of service as required. For VMware backups, there is one discovery job done for each policy, more number of policies there are more amount of discovery jobs would be running. Consolidating several policies can reduce the number of times vCenters are queried for the data. Careful consideration of all the VMware policies is recommended, especially in the case of a large VMware environment. Another consideration for grouping correct VMs in policies is to have better control over resource utilization across the NetBackup domain.
Advanced policy attribute - VMware Server List
This attribute is a mechanism to control which virtual machine servers that NetBackup communicates with for a given policy. In large virtual environments, you can use this list to improve backup/discovery performance. This mechanism can also be used to temporarily avoid a particular vCenter and ESX server, or to eliminate accessing vCenters that are known to not have VMs to be included in the policy.
DNS Configuration
NetBackup may be unable to identify virtual machines when you use the Browse for Virtual Machines dialog. Virtual machine hostnames may not be properly configured in your Domain Name Server system (DNS), or the DNS system may be slow.
In a large VMware environment, reverse name lookups can be very slow depending on the number of virtual machines being discovered. You can change the VNET_OPTIONS option to determine how many items NetBackup can cache.
Another option would be to use VM display name as the Primary VM identifier. This can address problems such as:
Host name/DNS not configured correctly
DNS server is slow to respond
However, if using VM display name as the Primary VM identifier, it is recommended that VM display name is set to same as the VM host name. If Primary VM identifier is different than the host name, while doing individual file and folder restores using the Backup, Archive and Restore (BAR) GUI, backup image selection might not happen automatically. Use the VM search feature to identify correct VM backups to restore from.
Note that each item in NBU's DNS cache takes about 1 KB in memory. This value is in the
bp.conffile on UNIX and Linux and the registry on Windows. See the NetBackup for VMware Administrator's Guide for details.