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
MSDP tuning considerations
The default MSDP configuration, defined in the contentrouter.cfg
file should work for most of the installations, in particular for storage pool size 95 TB or less and moderate workload environments.
For large servers that need to support a high number of concurrent jobs (400 or above) and a storage pool larger than 256 TB, some tunings listed in the following table may be necessary.
Table: MSDP tuning considerations
Parameter | Default value | Recommended value | Purpose |
---|---|---|---|
MaxCacheSize | 75% on older NeBackup versions | 50% | Limit the maximum amount of RAM used for fingerprint caching to 50% of the RAM. |
MaxConnections | 3000 | 8192 | Supporting large numbers of concurrent jobs. |
AllocationUnitSize | 2MiB | 8MiB | To avoid MSDP engine crashes with stack overflow caused by the process exceeding the maximum number of memory map areas that a process may have. The maximum number is defined by the Linux kernel parameter, max_map_count. For systems with RAM size greater than 512 GB, this tuning parameter is highly recommended |