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
Best practices: NetBackup tape drive cleaning
You can use the following tape drive cleaning methods in a NetBackup installation:
Frequency-based cleaning
TapeAlert (on-demand cleaning)
Robotic cleaning
Refer to the NetBackup Administrator's Guide, Volume II, for details on how to use these methods. Following are brief summaries of each method.
Table: Tape drive cleaning methods describes the three tape drive cleaning methods.
Table: Tape drive cleaning methods
Tape drive cleaning method | Description |
---|---|
Frequency-based cleaning | NetBackup performs frequency-based cleaning by tracking the number of hours a drive has been in use. When this time reaches a configurable parameter, NetBackup creates a job that mounts and exercises a cleaning tape. This practice cleans the drive in a preventive fashion. The advantage of this method is that typically no drives are unavailable awaiting cleaning. No limitation exists as to the platform type or robot type. On the downside, cleaning is done more often than necessary. Frequency-based cleaning adds system wear and takes time that can be used to write to the drive. This method is also hard to tune. When new tapes are used, drive cleaning is needed less frequently; the need for cleaning increases as the tape inventory ages. This method increases the amount of tuning administration that is needed and, consequently, the margin of error. |
TapeAlert (reactive cleaning, or on-demand cleaning) | TapeAlert (on-demand cleaning) allows reactive cleaning for most drive types. TapeAlert allows a tape drive to notify EMM when it needs to be cleaned. EMM then performs the cleaning. You must have a cleaning tape configured in at least one library slot to use this feature. TapeAlert is the recommended cleaning solution if it can be implemented. Certain drives at some firmware levels do not support this type of reactive cleaning. If reactive cleaning is not supported, frequency-based cleaning may be substituted. This solution is not vendor or platform specific. Veritas has not tested the specific firmware levels. The vendor should be able to confirm whether the TapeAlert feature is supported. See How NetBackup TapeAlert works. See Disabling TapeAlert. |
Robotic cleaning | Robotic cleaning is not proactive, and is not subject to the limitations of the other drive cleaning methods. Unnecessary cleanings are eliminated, and frequency tuning is not an issue. The drive can spend more time moving data, rather than in maintenance operations. NetBackup EMM does not support library-based cleaning for most robots, because robotic library and operating systems vendors implement this type of cleaning in different ways. |