That's pretty much what's fixed mine in the past. Go into your device manager and check the properties on the tape device and make sure on the "driver" tab, the provider is Symantec.
#Backup exec 2010 live update drivers#
Make sure you are using the Symantec provided drivers for the loader rather then the drivers that came with the loader. This is an old "fix" for tape drives/libraries/loaders etc, so maybe you've already done this. I predict that I'll have roughly the same failure rate. Have NO users on it, no internet, no outside influences and see how reliable the back ups are. I would like to isolate these from any other part of my network. An Exchange server, an SQL server, a file server and a BE 2010 (or any other version really, but 2010 had been the most miserable for me).
I swear, I want to do a test where I build a separate network. I currently have 2 - 2010 servers with two tape libraries. Then another job that's run perfectly for 9 months will fail for no reason and nothing will get it going again until you rebuild the job. Every morning is another seeming random job failure for no reason. As a result it's become more and more unreliable and unstable. It gradually starting getting bloated and unreasonably complicated. It was solid, it worked, it was simple and I couldn't stop saying good things about it. See, Backup Exec used to be a great product. Yeah, I'm pretty sure this is part of Symantec's "Random Error Generator" (REG).