Please enter search query.
Search <book_title>...
Veritas NetBackup™ Device Configuration Guide
Last Published:
2018-09-17
Product(s):
NetBackup (8.3.0.1, 8.3, 8.2, 8.1.2)
- Introducing device configuration
- Section I. Operating systems
- Linux
- About the required Linux SCSI drivers
- About configuring robot and drive control for Linux
- Solaris
- Installing/reinstalling the sg and the st drivers
- About Solaris robotic controls
- About Solaris tape drive device files
- Configuring Solaris SAN clients to recognize FT media servers
- Windows
- Linux
- Section II. Robotic storage devices
- Robot overview
- Oracle StorageTek ACSLS robots
- About removing tapes from ACS robots
- Robot inventory operations on ACS robots
- NetBackup robotic control, communication, and logging
- ACS robotic test utility
- ACS configurations supported
- Device configuration examples
acstest on UNIX systems
acstest depends on acsssi being started successfully. You can use the UNIX netstat -a command to verify that a process listens on the SSI socket. acstest attempts to communicate with ACS library software using acsssi and connects on an existing socket.
The usage format follows. You can pass the socket name on the command line. Otherwise, the default socket name (13741) is used.
acstest -r ACS_library_software_hostname [-s socket_name] [-d drive_path ACS, LSM, panel, drive] ... [-C sub_cmd]
The following example assumes that the acsssi process has been started by using socket 13741:
/usr/openv/volmgr/bin/acstest -r einstein -s 13741