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. Veritas NetBackup™ Device Configuration Guide
  3. Section II. Robotic storage devices
  4. Oracle StorageTek ACSLS robots
  5. NetBackup robotic control, communication, and logging
  6. NetBackup robotic control, communication, and logging for UNIX systems
  7. Using acssel with a different socket name
Veritas NetBackup™ Device Configuration Guide

Using acssel with a different socket name

If the vm.conf file does not contain an ACS_SEL_SOCKET entry, acssel listens on socket name 13740 by default.

You can change this default by using one of the following methods:

  • Modify the vm.conf configuration file.

    See To change the default by modifying the vm.conf configuration file.

  • Add environment variables. This method assumes that one ACS robot is configured and that the SSI default socket name has not been changed. (The vm.conf ACS_SEL_SOCKET entry can change the default).

    See To change the default by adding environment variables.

    acssel also has a command line option to specify the socket name. However, because acsssi needs to know the event logger socket name, setting an environment variable is preferred.

To change the default by modifying the vm.conf configuration file

  1. Edit the vm.conf file and add an ACS_SEL_SOCKET entry. The following is an example:

    ACS_SEL_SOCKET = 13799

  2. Stop the acsd, acsssi, and acssel processes by invoking the following script. (This script stops all NetBackup processes.)

    /usr/openv/NetBackup/bin/bp.kill_all

  3. Restart the NetBackup daemons and processes by invoking the following script:

    /usr/openv/NetBackup/bin/bp.start_all

To change the default by adding environment variables

  1. Stop the acsd, acsssi, and acssel processes by invoking the following script. (This script stops all NetBackup processes.)

    /usr/openv/NetBackup/bin/bp.kill_all

  2. Set the wanted socket name in an environment variable and export it. The following is an example:
    ACS_SEL_SOCKET = 13799
    export ACS_SEL_SOCKET
  3. Start the event logger in the background.

    /usr/openv/volmgr/bin/acssel &

  4. Set the ACS library software host name for acsssi in an environment variable.
    CSI_HOSTNAME = einstein
    export CSI_HOSTNAME
  5. Start acsssi as follows:

    /usr/openv/volmgr/bin/acsssi 13741 &

  6. Optionally, start acstest by using the robtest utility or by using the following command:

    /usr/openv/volmgr/bin/acstest -r einstein -s 13741

    If you request SCSI unloads, you also must specify drive paths on the acstest command line.

    The robtest utility specifies drive paths automatically if ACS drives have been configured.

  7. Start ltid as follows, which starts acsd. You can use the -v option for verbose message output.

    /usr/openv/volmgr/bin/ltid

    During initialization, acsd obtains the SSI Event Logger socket name from vm.conf and sets ACS_SEL_SOCKET in the environment before it starts acssel. If acsssi is started manually, it has to use (listen on) the same SSI socket that acsd uses to send data.

More Information

ACS robotic test utility

Feedback

Was this page helpful?
Previous

NetBackup ACS SSI event logger (acssel)

Next

NetBackup ACS storage server interface (acsssi)

Feedback

Was this page helpful?