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
Bypassing disk performance with the SKIP_DISK_WRITES touch file
The SKIP_DISK_WRITES procedure can be used on Linux/UNIX or Windows.
The SKIP_DISK_WRITES procedure is a useful follow-on to the bpbkar procedure. The bpbkar procedure may show that the disk read performance is not the bottleneck. If it is not the bottleneck, the bottleneck is in the data transfer between the client bpbkar process and the server bptm process. The following SKIP_DISK_WRITESprocedure may be helpful.
If the SKIP_DISK_WRITES procedure shows poor performance, the problem may involve the network, or shared memory (such as not enough buffers, or buffers that are too small). You can change shared memory settings.
Warning:
The following procedure can lead to data loss. The SKIP_DISK_WRITES touch file disables all backup data write operations for disk. It is not recommended to touch this file on a production server or data lost will occur. Disable active production policies for the duration of this test. You must remove the touch file when this test is complete. (See step 7.)
To bypass disk I/O using the SKIP_DISK_WRITES touch file
- Create a new disk storage unit, with /tmp or some other directory as the image directory path.
- Create a policy that uses the new disk storage unit.
- Deactivate any active production policies for the duration of this test.
- Create the SKIP_DISK_WRITES file.
Linux/UNIX:
/usr/openv/netbackup/db/config/SKIP_DISK_WRITES
Windows:
install_path\Netbackup\db\config\SKIP_DISK_WRITES
This file disables all data-write operations for disk backups but retains the creation of disk fragments and associated metadata.
- Run a backup from this policy.
NetBackup creates a file in the storage unit directory as if this backup is a real backup to disk. The image file is 0 bytes long.
- To remove the zero-length file and clear the NetBackup catalog of a backup that cannot be restored, run this command:
Linux/UNIX:
/usr/openv/netbackup/bin/admincmd/bpexpdate -backupid backupid -d 0
Windows:
install_path\Netbackup\bin\admincmd\bpexpdate -backupid backupid -d 0
Where backupid is the name of the file that resides in the storage unit directory.
- Remove the
SKIP_DISK_WRITES
file. - Re-activate any policies that were deactivated for this procedure.
More Information