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™ Logging Reference Guide
  3. Locating logs
  4. txxd and txxcd logging
Veritas NetBackup™ Logging Reference Guide

txxd and txxcd logging

The robotic daemon (txxd, where xx varies based on the type of robot being used) provides the interface between ltid and the tape library. The robotic control daemon (txxcd) provides the robotic control for the robot and communicates mount and unmount requests.

Log location

The txxd and txxcd processes do not have their own log files. Instead, errors are logged in the robots debug log and the system log. The system log is managed by syslog on UNIX and by the Event Viewer on Windows.

See UNIX logging with syslogd.

See Logging options with the Windows Event Viewer.

Logging method

The debug information is included by adding the word VERBOSE to the vm.conf file.

See How to control the amount of information written to legacy logging files.

On UNIX, debug information is also included by starting the daemon with the -v option (either by itself or through ltid).

More Information

Robots logging

Feedback

Was this page helpful?
Previous

tar logging

Next

vnetd logging

Feedback

Was this page helpful?