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
Forced rescan schedules
For virtualization technologies, such as VMware and Hyper-V, forced rescan schedules work differently than for files and folder backup. With files and folders, NetBackup maintains a track log to manage the change detection. However, with virtualization workloads, it is usually the virtualization vendor technology that provides the change detection.
Forced rescan mode in files and folder verifies information on the client file system with the information stored in the track log. For VMware backups, there is no track log, so there is no verification as such. Instead, forced rescan with virtualization workloads requests all blocks, regardless of any detected changes. This method ensures that all blocks are protected by that backup, which results in a full backup. The duration of the forced rescan backup takes longer and is similar to a non-Accelerator full backup.
For stable customer environments with proven technology stack, forced rescan schedules are not required for virtualization workloads. They can be used for troubleshooting and problem-solving purposes. For additional information on forced rescan for VMware, refer to the NetBackup fo VMware Adminstrator's Guide