Veritas NetBackup™ Device Configuration Guide
- Introducing device configuration
- Section I. Operating systems
- About the required Linux SCSI drivers
- About configuring robot and drive control for Linux
- 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
- 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
- NetBackup robotic control, communication, and logging for UNIX systems
- ACS robotic test utility
- ACS configurations supported
- Device configuration examples
NetBackup ACS SSI event logger (acssel)
The NetBackup ACS storage server interface (SSI) event logger acssel is modeled after the Oracle StorageTek mini_el event logger. Therefore, its functional model differs from other NetBackup robotic controls.
The NetBackup acsd daemon starts acssel automatically. You also can start it manually. Event messages are logged to the following file:
Veritas recommends that acssel run continuously because it tries to connect on the event logger's socket for its message logging. If acsssi cannot connect to acssel, NetBackup cannot process requests immediately. Therefore, retry and error recovery situations can occur.
On UNIX systems, only the kill command stops acssel. The NetBackup bp.kill_all utility (UNIX ) stops the acssel process. On Windows systems, the bpdown.exe program stops the acssel process.
The full path to the event logger is /usr/openv/volmgr/bin/acssel. The usage format is as follows:
acssel [-d] -s socket_name
The following describes the options:
-d displays debug messages (by default, debug messages are disabled).
socket_name is the socket name (or IP port) to listen on for messages.