• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1164
  • Last Modified:

NEO 4000 Robotic Arm not detected in Windows Device Manager

I have a WIN2K8 Server running Symantec BEX 2010 R2 attached to a Overland NEO 4000 tape library. Our backups started to fail yesterday after BEX started to generate errors. After talking with Symantec support, they think that the robotic library is having a problem as it's not being detected in Device Manager. I've rebooted both library and server. I've also flashed both tape library and tape drive to the latest firmware. Still no dice.
0
RAFF-
Asked:
RAFF-
  • 2
1 Solution
 
vvladaCommented:
Did you run diag on NEO? Sometimes only tape in NEO has a failure and you sholud be able to get this kind of info on NEO's display. It could be that tape unit inside library can't be detected and this could be the source of your problems. Run diag on NEO's front and see if everything is ok with library.
0
 
RAFF-Author Commented:
After working with Symantec, we had to shut down the server and media library for a few minuts to reset its self. Powered back on the media library and waited 60 seconds to power back the backup server. Once logged in, we proceeded to reinstall the drivers through Backup Exec. Once BEXEC and Windows detected the library in Device Manger as Medium Changer Devices, we were able to backup our data.
0
 
RAFF-Author Commented:
I was able to get this fixed with Symantec Support.
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now