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™ Administrator's Guide, Volume I
  3. Section III. Configuring storage
  4. Configuring robots and tape drives
  5. Correlating tape drives and device files on UNIX hosts
  6. UNIX device correlation example
Veritas NetBackup™ Administrator's Guide, Volume I

UNIX device correlation example

On UNIX only.

Assume a TLD robot includes three drives and the operating system includes the following device paths:

Drive 1

/dev/rmt/0cbn

Drive 2

/dev/rmt/1cbn

Drive 3

/dev/rmt/3cbn

Also assume that you requested that the tape be mounted on drive 1.

If the device path for the drive is configured correctly, the NetBackup Administration Console Device Monitor shows that the tape is mounted on drive 1.

If the Device Monitor shows that the tape is mounted on a different drive, the device path for that drive is not configured correctly. For example, if the Device Monitor shows that the tape is mounted on Drive 2, the device path for drive 1 is incorrect. Replace the drive 1 device path (/dev/rmt/0cbn) with the correct device path (/dev/rmt/1cbn) for drive 2. You may need to use a temporary device path while you make these changes. You also know that the device path for drive 2 is incorrect. Possibly, the device paths were swapped during configuration.

Use the robotic test utility to unload and unmount the tape from drive 1. Repeat the test for each drive.

If the path to the drive where the tape is mounted is not on the host with direct robotic control, you may have to unload the drive with a command from another host or from the drive's front panel.

Feedback

Was this page helpful?
Previous

Correlating tape drives and device files on UNIX hosts

Next

Managing tape drives

Feedback

Was this page helpful?