01-01-2014 10:14 AM
Hi Guys,
I installed Backup Exec 12.5 on my system Windows 2003. All backup are fine before this but recently about two weeks my HP MSL5000 tape library goes offline when inactive.
Appreciate is someone who have a lot of experince out there to share what are the cause of this tape library failing. Notice that it is hardware issue but I like to know what are the prefered solution from 'backup' expert out there
01-02-2014 05:31 PM
To detect any hardware error, run the HP LT&T utility against the tape library/drive. Make sure you select the write test and that you have stopped all the BE services beforehand. Also, update the firmware of the tape library and tape drive to the latest.
Make sure that the tape library appears in the Windows Device Manager as an Unknown Medium Changer with a Microsoft driver and that the tape drive has a Symantec driver.
You might also want to unplug and reseat the cable connnecting the tape library and tape drive to the machine.
01-03-2014 07:00 AM
...if you have the Removable Storage service still active and running in Windows, it can mess up BE's lock on the library. Check to see if this is so, and then stop/disable it. Restart the BE services and then try again.
Thanks!
01-03-2014 11:41 AM
I recommend connecting to the library's Remote Management Interface to determine the health of the unit. The very first button on the main menu is 'Status' and can quickly help you identify if there is a problem. Simply browse to the IP addressed assigned to the tape library and you'll be prompted for the login credentials.
If you do not have the library on the network, then physically go to the unit and login to the LCD console of it and do the same as I mentioned above.
The RMI and LCD have the same functions...more or less...
Good luck!
01-03-2014 11:47 AM
in addition check out Windows Event System Logs Errors
such as: Event ID 5.SCSI parity errors. This error can be caused by a faulty SCSI card or a faulty SCSI termination.
01-03-2014 12:10 PM
LTT is more comprehensive and can pull detailed logs which is probably why this is suggested for use.
What the console and web front-end have is cut-down.
Thanks.