Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. NetBackup™ Backup Planning and Performance Tuning Guide
  3. Measuring Performance
  4. Evaluating system components
  5. Bypassing disk performance with the SKIP_DISK_WRITES touch file
NetBackup™ Backup Planning and Performance Tuning Guide

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

  1. Create a new disk storage unit, with /tmp or some other directory as the image directory path.
  2. Create a policy that uses the new disk storage unit.
  3. Deactivate any active production policies for the duration of this test.
  4. 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.

  5. 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.

  6. 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.

  7. Remove the SKIP_DISK_WRITES file.
  8. Re-activate any policies that were deactivated for this procedure.

More Information

About shared memory (number and size of data buffers)

Feedback

Was this page helpful?
Previous

Measuring performance with bpbkar

Next

Measuring performance with the GEN_DATA directive (Linux/UNIX)

Feedback

Was this page helpful?