Once the wizard is completed go to Windows Device Manager and check to see if the drivers got installed. It will display "Quantum 1" indicating the autoloader with "Certance 1" indicating the drive under Robotic Libraries in Devices view in BE. BE should recognize your drive as "Certance Ultrium 2 SCSI Sequential Device". Go through the wizard making sure to use the Symantec drivers. Navigate to C:\Program Files\Veritas\Backup Exec\NT and find the file named "tapeinst.exe". You must use the Symantec drivers for it to work properly. Windows should recognize the Superloader upon logging in. Shut down the server and then reconnect the SCSI cable. At this time make sure that the latest tape device drivers are installed for BE and make sure that "Enable Robotic Library Support" feature is installed. Navigate to %SystemRoot%\System32\ and check to see if the file QmCox32.dll is there. Navigate to %SystemRoot%\System32\Drivers and check to see if the file QsmcX32.sys is there. Boot the server without the Superloader attached. It could also be listed under Unknown Devices depending on the installation procedure last taken. Go to Device Manager and uninstall it from under Medium Changers and Tape Drives. With the autoloader attached, remove it from the BE program device list. To get it to work properly you're going to need to start out fresh. I'll try my best relive those steps.ĭuring this whole ordeal I made sure I had the latest firmware for my Superloader and Adaptec SCSI card along with the latest Superloader drivers and BE device drivers from their repective websites. It took me a few days of uninstalling and reinstalling drivers to get the right combination. It was a nightmare setting it up, even with 10d. I had the exact same problem with my Superloader 3. Hope this helps you, and possibly me too! When the library started getting offline, the "\\.\MediumChanger0" went missing from the discovery. When library was able to get online in my case, there was a "\\.\MediumChanger0" information as well as a "\\.\Tape0" info. If you search up from that point in the file, you'll also see the last time the library was online.Īnother thing I added in my support case was the part of the log above those mentioned before. If you do have a similar problem, you will find that your library is being listed by string, has no "device name" and BE puts it offline. When it opens the resulting file, do a search for "offline". Run BEDiag (you can access it simply with "tools" and it's under backup services). Anyway, maybe this will help you and your tech support to get closer to the problem: However, I now have a problem similar to yours, with an open case as well, and still no solution. I had a bad experience upgrading 10d to 11d, got some major problems, reverted back to 10d. With the exception of the one tech, Raymond, no one has been able to help. We have the 24x7 support contract that I feel has been a waste of money. Surely there is someone out there that has the answer. We went back through all the steps the tech led us through but we have not been able to get the Superloader to be seen as an autoloader again. Neither one of the tape devices were found. Unfortunately, we had to reboot the server the next day due to the Daylight Savings Time updates. It worked like a charm and we were able to set up the backup jobs and partitions with no problems. One of the techs got everything to work once and we even did a test backup to the Superloader. We always have to manually start the BE services because only a couple of them load. We remove the tape devices and their drivers, reboot the server and reinstall the devices and drivers. The techs have had us uninstall, reinstall, and repair Backup Exec. Most of the time it is listed as a standalone tape drive and offline. Can someone please help? Backup Exec 11d for Windows Small Business Server 2003 Premium Edition does not see the Superloader 3 as a robotic library. We have been working with support for almost 3 weeks and do not have a solution yet.
0 Comments
Leave a Reply. |