NetBackup™ Backup Planning and Performance Tuning Guide
- NetBackup capacity planning
- Primary server configuration guidelines
- Media server configuration guidelines
- NetBackup hardware design and tuning considerations
- About NetBackup Media Server Deduplication (MSDP)
- MSDP tuning considerations
- MSDP sizing considerations
- Accelerator performance considerations
- Media configuration guidelines
- How to identify performance bottlenecks
- Best practices
- Best practices: NetBackup AdvancedDisk
- Best practices: NetBackup tape drive cleaning
- Best practices: Universal shares
- NetBackup for VMware sizing and best practices
- Best practices: Storage lifecycle policies (SLPs)
- Measuring Performance
- Table of NetBackup All Log Entries report
- Evaluating system components
- Tuning the NetBackup 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)
- About the communication between NetBackup client and media server
- Effect of fragment size on NetBackup restores
- Other NetBackup restore performance issues
- About shared memory (number and size of data buffers)
- Tuning other NetBackup components
- How to improve NetBackup resource allocation
- How to improve FlashBackup performance
- Tuning disk I/O performance
NetBackup client performance in the data transfer path
Many factors can affect the NetBackup client component of the NetBackup data transfer path. Consider the following to identify possible changes that may improve NetBackup performance:NetBackup
Table: Factors that affect the client component of the NetBackup data transfer path
Factors | Notes |
---|---|
Disk fragmentation | Fragmentation severely affects the data transfer rate from the disk. Fragmentation can be repaired using disk management utility software. |
Number of disks | Add disks to the system to increase performance. If multiple processes attempt to log data simultaneously, divide the data among multiple physical disks. |
Disk arrays | Convert to a system that is based on a Redundant Array of Inexpensive Disks (RAID). RAID devices generally offer greater throughput and (depending on the RAID level) improves reliability. |
SAN client | For critical data that requires high bandwidth for backups, consider the SAN client feature. Refer to the SAN Client and Fibre Transport Guide. |
Type of controller technology that drives the disk | Different controller technology could yield different results. |
Virus scanning | Virus scanning can severely affect the performance of the NetBackup client, especially for systems such as large Windows file servers. Consider disabling virus scans during backup or restore. |
NetBackup notify scripts | The NetBackup notify scripts are very useful in certain situations, such as shutting down a running application to back up its data. However, these scripts must be written with care to avoid any unnecessary lengthy delays at the start or end of the backup. If the scripts do not perform tasks essential to the backup, remove them. Linux/UNIX notify scripts:
Windows notify scripts:
|
NetBackup software location | If the data being backed up is on the same physical disk as the NetBackup installation, note: performance may be adversely affected, especially if NetBackup debug log files are generated. If logs are used, the extent of the degradation is greatly influenced by the logs' verbose setting. If possible, install NetBackup on a separate physical disk to avoid disk drive contention. |
Snapshots (hardware or software) | If snapshots are taken before the backup of data, the time that is needed to take the snapshot can affect the performance. |
NetBackup Client Job Tracker | If the Job Tracker is running on the client, NetBackup estimates the data to be backed up before the backup. Gathering this estimate affects the startup time and the data throughput rate, because no data is written to the NetBackup server during this estimation. Note: The Job Tracker is disabled by default. If it is launched, it runs until the user logs out. Avoid running the NetBackup Client Job Tracker if the data-gathering process takes too long. |
Determine the theoretical performance of the NetBackup client software | Use the NetBackup client command bpbkar (Linux/UNIX) or bpbkar32 (Windows) to determine how fast the NetBackup client can read the data to be backed up. You may be able to eliminate data read speed as a performance bottleneck. |
More Information
About measuring performance independent of tape or disk output