How to verify device configuration using robtest

The process to absolutely verify that the drive path mapping is correct on all of the media servers is a bit time consuming, but will ensure that everything is correct.

Step 1
Please note that this test cannot be run while NetBackup is attempting backups, restores, duplicates, or any other actions that involve the robot and drives.

Step 2
Acquire the output of " /usr/openv/volmgr/bin/tpconfig -d " from each of the media servers. This is the drive configuration within NetBackup for each server.

Step 3
On the robotic control host (probably the master), run /usr/openv/volmgr/bin/robtest. Keep this running during the entire procedure. After selecting the robot, it asks you to enter commands; enter : s d.

This will give the status of the drives. Make sure that none of the drives contain a tape. If they do, remove the tapes and place them back into slots.
The command to run a status of all the slots (to find empty ones) is : s s.
The command to unload a tape from drive 1 is : unload d1
The command to move a tape from drive 1 to slot 15 is : m d1 s15

If the unload or move commands return any errors, you will need to manually eject the tapes from the robot and move them into slots.

Step 4
Once there are no tapes in any of the drives, move a tape (that is not a cleaning tape) into drive 1.
The command to move a tape from slot 5 to drive 1 is: m s5 d1.
Now, from the command line of each server, run the following:

mt -f /dev/rmt/0cbn status

The specific path ( /dev/rmt/0cbn) will be determined by the output of the tpconfig -d command for each server. The path to any given robotic drive may not be the same on each media server.

If the command returns a message indicating that there is no tape loaded or the drive is offline, you will need to manually determine which device path is correct for drive 1 on that server. Do this by running through all the possible device paths until the correct one is determined:

mt -f /dev/rmt/1cbn status
mt -f /dev/rmt/2cbn status
mt -f /dev/rmt/3cbn status
...etc...

Do not change anything at this point. Simply make note of any device paths that need to be corrected.

Step 5
Once you have run through the drive path verification on each of the media servers, unload the tape from robtest.
The command to unload a tape from drive 1 is : unload d1
If the unload fails, the command to SCSI unload the drive is :
mt -f /dev/rmt/0cbn offline (device path specific to the server and drive being run on)
Once the tape is unloaded, move it to the next drive.
The command to move a tape from drive 1 to drive 2 is: m d1 d2

Step 6
Repeat steps 4 and 5 for each of the drives. When you are done, you will have an accurate mapping of all the drive device paths for each server.
Using the GUI or tpconfig , modify the device paths as needed, only restarting the NetBackup daemons after all changes have been made (otherwise it will take too long).

For IRIX, the mt command is identical, but the device path names look different.

In Windows, the native Windows backup application can be used as a secondary source of information about the media and the devices. Consult the operating system documentation or help menu for instructions on using the native Windows backup application.

 

An alternative solution is:

 

1. 

Unix

/usr/openv/volmgr/bin/

Windows

<installpath>\veritas\volmgr\bin

scan -changer 

determines the serial number  of each tape drive in the tape library and their physical position.

 

2. 

Then on any Media Server run 

Unix

/usr/openv/volmgr/bin/

Windows

<installpath>\veritas\volmgr\bin

tpautoconf -t
 
to get the tapedrive serial number and corresponding device path for that Media Server. 

Lastly, run tpconfig -d on the Media Server to see if the physical position matches the correct device path.