Netbackup 6.5 on Windows 2003 MSCS cluster + Overland Neo 4000 robot

[Pappo]

Hi Guys:

Our installation is two Overland Neo 4000 robots connected to the SAN with a NeoViaFCO3 bridge card. Each robot has two LTO-3 HP drives.
We installed Netbackup 6.5 on a MSCS cluster (Windows 2003 Server R2 with SP2)
After configuring the drives/robost with tpautoconf -a we started our test and find out that we are having some problems with the drives that have Robot Drive Number equal to 2 on each robot.
Every time we start a backup in these driver, it finishes with the following error:


16/07/2008 12:05:59 PM - started process bpbrm (1504)
16/07/2008 12:05:59 PM - connecting
16/07/2008 12:06:00 PM - connected; connect time: 00:00:01
16/07/2008 12:06:02 PM - mounting CAR601
16/07/2008 12:06:40 PM - mounted; mount time: 00:00:38
16/07/2008 12:06:43 PM - positioning CAR601 to file 6
16/07/2008 12:07:07 PM - positioned CAR601; position time: 00:00:24
16/07/2008 12:07:07 PM - begin writing
16/07/2008 12:09:26 PM - Error bptm(pid=2836) cannot write image to media id CAR601, drive index 1, No media in drive.
16/07/2008 12:09:29 PM - end writing; write time: 00:02:22
media write error(84)

Any ideas ?

Thanks in advance

Pappo 

[Andy_Welburn]

Sounds like your drives are misconfigured.

From the Admin Guide:

"...

Robot drive number
Specifies the physical location in the robot of the drive. When you add more than one drive to a robot, you can add the physical drives in any order. For example, you can add drive 2 before drive 1.
The correct robot drive number is critical to the proper mounting and utilization of media. You must determine which logical device name (Windows) or the device file (UNIX) identifies which physical drive in the robot. You should correlate the drive serial number with drive serial number information from the robot.
See “Correlating device files to physical drives when adding drives” in the
NetBackup Administrator’s Guide for Windows, Volume II
NetBackup does not detect incorrect drive number assignment during configuration; however, an error occurs when NetBackup tries to mount media on the drive.

..."

I would check the Serial Numbers on the tape drives with those identified by NetBackup and ensure that their locations match. When our library was first configured we didn't pay close attention to this & ended up with incorrectly labelled tapes etc etc. It looks like yours is loading a tape in one & checking to see if it's loaded in ther other!

[Omar_Villa]

Try controling the library with robtest and mount some tapes in to the drives is you can do this your OS is properly configured if not there is something wrong with the configuration, if this works then you can move to netbackup and check if tpconfig, tpautoconf and vmglob DB matchs the drive serial number, name and path.

regards