robot keeps going down following 84 error

[john_wotherspoo]

Hi there,

We are using NB 6.4 on solaris 10 and are having problems when we get 84 media write errors.  Any time we get a write error the robot goes down and i have to manually up the drive before it continues with other jobs.  Is there any way to stop the drive going down, or to auto up the robot if it goes down?

thanks in advance.

[Stefaan_M]

Hi,

I assume that you mean that the drive goes down and not the robot.

If Netbackup detects errors during the backup/restore, it will down the drive and freeze the tape.

I don't think there is a way to avoid this.

Stefaan.

[john_wotherspoo]

Yeah sorry, the drive goes down.

It never freezes the tapes, but always downs the drive, its a pain.  Looking to run a script that checks if a daemon is running thats tied to the drive being up, and if its down to automatically up it again.  Not sure on the daemons though.

[Stumpr2]

physically verify the drive mapping

[john_wotherspoo]

sorry, maybe me being stupid but... ???

[MariuszByczynsk]

Hi

Please try this. This script checks if drive is brought up.

http://mian.homepage.dk/ksh/drivewatch.html

[john_wotherspoo]

cool stuff, i will check this out and let you know if it worked.

thanks.

[john_wotherspoo]

# /usr/openv/volmgr/bin/vmoprcmd -upbyname DRIVENAME

IT WORRKKKKSSSSS :D

Thanks LOADS m8, life saver.  

[Panther]

is there a solution like this for windows version??

[Omar_Villa]

Drives will always go down if there is a missmatch between the tpconfig, tpautoconf and vmglob DB's if they dont match in Drive Serial Number, Drive Name and Path then you will get all kind of media errors and drives going down.

regards

[Franck_Paris]

Panther, the vmoprcmd command works on windows too.