robtest issue and robot inventory issue

[cstorm]

I am having a problem with a new NetBackup install. My environment is HPUX 11i with NBU 4.5. Tape Storage unit is an STK L20. The robtest utility successfully moves tapes from the CAP to slots and from slots to drives. However, the move from drives to slots is unsuccessful.

Also, the inventory of the robot shows (using NBU GUI) shows that the tapes are in slots, even though the tapes are physically mounted in the tape drives. Has anyone had similar problems and what are suggested remedies?

 

[Stumpr]

Remember to issue an unload before attempting to move a tape from the drive to its slot position.
unload d1
m d1 s1

Also The server that you run robtest from must have scsii acess to the drive. If it doesn't then log onto the server that does have scsii and use the UNIX command
#mt <tapepathname> offl
to unload the tape from the drive. Then you can use robtest to move it from the drive to the slot.

 

[cstorm]

Thanks for the input. I have found that if I specify the other tape drive in the library, it unloads fine.

Example:

mv s5 d1 Loads the tape into drive1
unload d1 Unloads the tape in drive1
mv d1 s5 Gives and error indicating no tape in drive1
mv d2 s5 Successfully moves the tape from drive1 to slot5

I have tested this on drive2 and it works the same (backwards) way. Have you seen this before?

 

[OHWS]

Not sure if this is your issue or not. I'm assuming this is a new setup that you have. You may have the drive path for example /dev/rmt/DLT4 mixed up??? Try and write down your current setup then delete both of the drives in question and set them up using the opposite drive path.
This may or may not be your issue I've just seen something similar in the past. Hope this helps!

 

[cstorm]

Thanks for the replies. This problem has been resolved. The problem had to do with the path addressing of the devices. I thought that /dev/sctl/c4t0d0BESTnb would be seen by the robot as drive1 and that /dev/sctl/c4t0d1BESTnb would be seen as drive2. This was not the case. Just the opposite.

I used the tpconfig utility to correct the problem. Example:

* Rename the robot db files:
cd /usr/openv/volmgr/database
mv robotic_def old.robotic_def
mv ltidevs old.ltidevs

* Configure the robo and tape drive paths:
/usr/openv/volmgr/tpconfig

robtest works fine now.

Thanks