Solved

NEO 4000 Robotic Arm not detected in Windows Device Manager

Posted on 2011-02-23
3
1,131 Views
Last Modified: 2012-05-11
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
Comment
Question by:RAFF-
  • 2
3 Comments
 
LVL 7

Expert Comment

by:vvlada
ID: 34963337
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
 

Accepted Solution

by:
RAFF- earned 0 total points
ID: 35019570
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
 

Author Closing Comment

by:RAFF-
ID: 35067659
I was able to get this fixed with Symantec Support.
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Monitor input from a computer is usually nothing special.  In this instance it prevented anyone from using the computer.  This was a preconfiguration that didn't work.
Great sound, comfort and fit, excellent build quality, versatility, compatibility. These are just some of the many reasons for choosing a headset from Sennheiser.
This tutorial will walk an individual through locating and launching the BEUtility application and how to execute it on the appropriate database. Log onto the server running the Backup Exec database. In a larger environment, this would generally be …
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…

820 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question