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. Robot overview
  5. Robotic processes
  6. Robotic process example
Veritas NetBackup™ Device Configuration Guide

Robotic process example

Each drive in a tape library DLT (TLD) robot can be attached to a different host, and a tldd process runs on each host. However, only one host controls the robotics, and the tldcd robotic control process runs on that host only. To mount a tape, the tldd process on the host to which the drive is attached sends control information to the tldcd process on the robotic control host.

The following figure shows the processes and where they run for a TLD robot.

Figure: TLD robot control process example

TLD robot control process example

The following describes this example:

  • Each host connects to one drive, and a tldd robotic process runs on each host.

  • The robotic control and therefore the robotic control process, tldcd, is on host A.

The NetBackup Device Manager services on host A and B start tldd. The tldd process on host A also starts tldcd. Requests to mount tapes from host B go to tldd on host B, which then sends the robotic command to tldcd on host A.

More Information

NetBackup robot types

Feedback

Was this page helpful?
Previous

Processes by robot type

Next

Oracle StorageTek ACSLS robots

Feedback

Was this page helpful?