How to identify drive path

Hi,

Take a look this part, from NetBackup™ Administrator's Guide Volume I, and let us know of this can help you.

Correlating tape drives and device files on UNIX hosts
If your tape drives do not support device serialization, you may have to determinewhich device file or SCSI address matches the physical drive. You also may have to do so if you add the tape drives manually.
Correlate device files to physical drives when you create the device files for each drive.

To correlate tape drives and device files on UNIX

1 Determine the physical location of each drive within the robotic library. The location usually is shown on the connectors to the drives or in the vendor’s documentation.
2 Physically connect the drives to SCSI adapters in the host.
3 Record the adapter and SCSI addresses to which you connected each drive.
4 Create device files for each drive by using the SCSI addresses of the drives and adapters. Add the device file by using the notes from a previous step to complete the correlation between device files and physical drive location.
5 Configure the robot in NetBackup and then add the drives. When you add the drives, verify that you assign the correct drive address (for example, robot drive number) to each device path.Optionally, use the appropriate NetBackup robotic test utility to verify the configuration. Information about the robotic test utilities is available.
See NetBackup Troubleshooting Guide: http://www.veritas.com/docs/DOC5332

To verify the device correlation on UNIX
1 Stop the NetBackup device daemon (ltid).
2 Start ltid, which starts the Automatic Volume Recognition daemon (avrd). Stop and restart ltid to ensure that the current device configuration is activated. If robotic control is not local to this host, also start the remote robotic controldaemon.
3 Use the robotic test utility to mount a tape on a drive.
4 Use the NetBackup Administration Console Device Monitor to verify that the tape was mounted on the correct robot drive.

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 drive1.
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.