Link to home
Avatar of rbichon
rbichon

asked on

Superloader 3 and Backup Exec 12

I am having a heck of a time getting this thing to work with Backup Exec 12. It is using the Symantec drivers, is listed in the Robotic Libraries, and the DLT-V4 drive is listed under the library. 15 of the slots in the autoloader have DLT-VS1 tapes in them and the 16th has a cleaning cartridge. But for some reason, even when I try to test the back job, Backup Exec is never able to access the autoloader...and I would know because it is loud! Does anyone have a step by step guide on how to do this? Any info at this point would be great. Thanks.

Here is a screen shot of the devices page. Maybe I am missing something...
backupexec12.jpg
Avatar of dot45
dot45

I see two drives in your screenshot, do you have dual drives in the unit or a seperate drive also attached?

I would remove the drive and loader from within backupexec and the device listing from device manager. Reboot, then re-add them.
Avatar of rbichon

ASKER

The one listed as QUANTUM 1 is my original stand-alone drive which I kept in the server just in case I need it. QUANTUM 2 is the drive that is located in the SuperLoader 3.

I did a full diagnostic on the loader using xTalk from Quantum and all of the tests passed. It is probably worth while to mention that I am using the latest Quantum drivers, not Symantec's because they causing errors in the Event Viewer. Also, I just noticed that I was supposed to update the firmware on the drive before updating the firmware on the library...which I did not do. So, I re-ran the firmware upgrade on the library just now. I am going to try your suggestions and see what happens. Hopefully I did not inadvertantly screw myself!
Avatar of rbichon

ASKER

It is also good to note that originally QUANTUM 2 was listed under stand-alone drives, not the library. I had to go into the device wizard and associate the drive with the library. It seems to me that it should have associated them together automatically. Is that correct?
I will have to check our autoloader at work, Its a superloader3 but we only have a LTO2 drive it in.
Avatar of rbichon

ASKER

I think I am making progress. I still can't get BE 12 working but I did get BE 11d working. Also, I found this link http://seer.entsupport.symantec.com/docs/190653.htm that told me to enable Multiple LUN Support in the SCSI controllers BIOS for the SCSI ID that the superloader is installed on. Once I did that both the library and the drive showed up during POST under the SCSI devices list. I think that might be a big key. Once I verify that all of the functions I need work under BE 11d, I am going to try BE 12 again.

Another thing to note is that BE 11d automatically associated the SCSI drive with the library...BE 12 had to be associated manually. I think that is a key piece of the puzzle.
ASKER CERTIFIED SOLUTION
Avatar of dot45
dot45

Blurred text
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
Avatar of rbichon

ASKER

I went ahead and tried to reinstall BE 12...no go. Same problem as before. So I went through the downgrade process again and BE 11d still works. I guess we do have some compatibility issues with the new software. Oh well, thanks for your help.