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. Tuning the NetBackup data transfer path
  4. NetBackup network performance in the data transfer path
  5. Using socket communications (the NOSHM file)
NetBackup™ Backup Planning and Performance Tuning Guide

Using socket communications (the NOSHM file)

When a primary server or media server backs itself up, NetBackup uses shared memory to speed up the backup. In this case, NetBackup uses shared memory rather than socket communications to transport the data between processes. However, it may not be possible or desirable to use shared memory during a backup. In that case, you can use socket communications rather than shared memory to interchange the backup data.

To use socket communications

  • Touch the following file:

    Linux/UNIX

    /usr/openv/netbackup/NOSHM

    Windows

    install_path\NetBackup\NOSHM

    To touch a file means to change the file's modification and access times. The file name should not contain any extension.

Feedback

Was this page helpful?
Previous

About the NOSHM file

Next

NetBackup server performance in the data transfer path

Feedback

Was this page helpful?