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
About performance hierarchy level 1
Level 1 is the storage portion of a typical disk array. It can be populated with various size of Hard Disk Drives (HDD), typically 7200RPM SAS (Serial Attach SCSI (Small Computer System Interface)) that are dual ported to provide high availability. The storage can also be configured with Solid State Drives (SSD) for environments where access time is critical, such as concurrent read/write operations. As an example, backups with immediate replication to a remote site would benefit from SSDs. HDDs and SSDs are available in SAS configurations as SAS provides a redundant, reliable, mature protocol.
SAS runs at a speed of 12Gb/s in this example. The connectivity from the RAID controllers as well as the controllers themselves are noted with the purple lines and outlines. The connectivity from the controllers to the drives are 12Gb and the drives have a dual ported connection. Each of the drive SAS ports are connected via a SAS fabric with "expander" that allows for a high number of concurrent connections to disks, SSDs, tapes, and RAID controllers. The dual port connection allows for dual controller operation, the whole of which produces a highly reliable solution with 99.999% (5 nines) of availability. This solution is used primarily on the higher capacity systems that require speed and availability as key requirements.
When using disk drives of 1TB or higher capacity, it is highly recommended that users build their systems with RAID 6/dual parity or RAID 10 to ensure that no data is lost due to disk failures. Systems with the size of drives equal to or greater than 1TB take a relatively long time to rebuild to a hot spare that should be included in every system. The long rebuild time creates a need to plan against a second drive failure during rebuild. RAID 6 addresses this as its configuration provides two parity drives.
When creating storage, note that NetBackup supports volumes of up to 32 TiB and a maximum of 6 volumes per NetBackup Media server, so decide on your storage solution with this in mind. As an example, if 4TB drives were used and the volume had 11 drives configured in a RAID6 Logical Unit Number (LUN) the effective capacity in TB would be 4 * (11-2) = 36TB. In TebiBytes (TiB) it converts to 32.74 TiB.
This same type of solution can be created with SSDs. A major consideration is that the speed of rebuild for a disk drive is much longer than an SSD. Rebuilds with a 7.68TB SSD are approximately, 2.25 hours as compared to the 4TB disk drive noted earlier which, if there are numerous volumes being managed by dual controllers, can stretch to 40+ hours. Because of this difference in rebuild speed, with SSD drives, it is possible to build RAID5 volumes and have a fast enough rebuild to remove the need for dual parity. Use cases for SSD include re-hydration of deduplicated data to save to tape and operations, such as multiple concurrent backups and replications.