text: How to troubleshoot issues with a Robotic Library (autoloader/changer) or Tape Drive in Backup Exec for Windows Servers
  Mark Bellows Sep 12, 2009 | Comment (1)
  One of the frequent issues that I hear about is issues with tape drives and robotic libraries working correctly. One of the first things to check is the compatibility of the hardware, especially if it older. Symantec has and HCL (hardware compatibility list) located here:
  http://www.symantec.com/business/support/documentation.jsp?language=english&view=compπd=15047
  Although a unit may work to begin with, Symantec will remove older hardware from time to time. If you have updated Backup Exec with the latest drivers, this may be your problem. ALWAYS check this list of hardware changes that is listed with the driver to ensure ALL of your hardware is listed. Do not look for just the library - the drive may be supported even though the library itself is.
  I have dealt with several different vendors of hardware and I can tell you that all of them can encounter issues.
  Over time I have discovered the SCSI attached devices have far more problems than ISCI or fibre connected hardware. The typical issue tends to be the failure of the terminator at the end of the SCSI path and it is the first thing I check.
  Another common resolution includes updating / reapplying the firmware for all hardware involved (whether SCSI, ISCSI or fibre, this still applies).
  One thing that I have realized, and I have myself been a victim of, is skipping over the basic things, such as checking cables to ensure they have not damaged or loss their connection. I had a colleague install a server in the same rack a tape library was in. In the process of doing so, he needed a little room to run network cables through, so he had moved the SCSI cable out of the way. When he was done, he closed the rack door, only to find that he had not put the SCSI cable back. It got pinched in the door. He did not realize it had been damaged and just put it back in place.
  I started having trouble with the tape library that this cable was connected to. After a couple of hours of troubleshooting, I discovered the nick in the cable. Once I replace the cable, the unit came back online without any issue.
  One last note on this. When working a Windows environment, be very careful not to allow driver updates for cards or NICs, as these can cause issues with operations as well.
  Here is a link to the documentation that Symantec has published. It has the steps to troubleshoot the issue.
  Document ID: 255501
  If you are having issues, and this does not resolve it, post your issue. Include the as much information as you can so we can help you track it down faster.
  USER_1975710 Apr 10, 2010
  Hi, we are having problem backing Oracle server; the error message is "Backup- Oracle-Win::\\oracle server\xxxxxThe Database script returned an error. Refer to the Database script output section in job logs for more details."