Please enter search query.
Search <book_title>...
NetBackup™ Backup Planning and Performance Tuning Guide
Last Published:
2024-04-16
Product(s):
NetBackup & Alta Data Protection (10.4, 10.3.0.1, 10.3, 10.2.0.1, 10.2, 10.1.1, 10.1, 10.0.0.1, 10.0, 9.1.0.1, 9.1, 9.0.0.1, 9.0, 8.3.0.2, 8.3.0.1, 8.3)
- 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
Replication and duplication of backups
When replicating or duplicating images between pools, data commonality should be considered. Consider the case of two sites replicating bi-directionally. Each site has clients that are protected and sends those backups to the other site. If there is common data between the sites (for example, copies of databases), the data will not have to be written at the remote site, since it already exists in the storage pool. This can result in significant space savings depending on the level of data commonality. If there are large quantities of common data, this should be considered when sizing. If there is limited or no commonality, then the space consumed on the remote pool will be about the same as the space consumed locally for those backups.