BExec 9.0 adding an autoloader: showing as standalone

[Steve_Levine]

I have a long-standing installation of Backup Exec 9.0 build 4454 on Win2K SP4. I've been using an ADIC Fastor DLT8000 autoloader successfully. My storage requirements have exceeded its capacity, so I'm adding a Quantum SDLT320 autoloader to the server.

The two drives are daisychained, with the new drive sitting between the host and the old one.

The new drive keeps coming up as a standalone drive. I've tried running tapeinst.exe several times, including removeing and reinstalling all devices. The OS sees it as it should be.

How do I fix?

[Steve_Levine]

More Info: I tried removing the older library and connecting the Quantum drive alone, but with no change.

[priya_khire]

Hello,

Backup Exec provides support for unlimited standalone tape drives. However in case of libraries or autoloaders, the first drive can be used but you need to purchase the Library Expansion Option for every additional drive. In case you have not purchased it, it can be causing the problem.

If the status is not as mentioned above, do elaborate the licenses you have. Does the drive not appear at all or is it seen online as a standalone drive? Are you able to run device operations on that?

M ake sure that you have updated Backup Exec v9.0 to Backup Exec v9.1. It addresses many issues and enhancements from an earlier versions and Build of Backup Exec v9.0. Refer the following technotes:

Title: VERITAS Backup Exec (tm) 9.1 for Windows Servers revision 4691.1 (Single .ZIP download)
http://seer.support.veritas.com/docs/264658.htm

Title: VERITAS Backup Exec (tm) 9.1 for Windows Servers General Information
http://seer.support.veritas.com/docs/262414.htm

Note: 1. BEWS 9.1 is a free downloadable upgrade inclusive of previously installed agents and options from Backup Exec 9.0 for Windows Servers agents and options.

2. Update all agents/options on all remote systems.

Additional Information :
For information on the recent VERITAS Backup Exec security vulnerabilities, including links to the downloads for the necessary hotfixes, please refer to the following document:
Patch summary for Security Advisories VX05-001, VX05-002, VX05-003, VX05-005, VX05-006, VX05-007

http://seer.support.veritas.com/docs/277429.htm

Note : If we do not receive your reply within two business days, this post would be marked ‘assumed answered’ and would be moved to ‘answered questions’ pool.


Regards.

[Steve_Levine]

So what you're saying is that if I'd only hooked up the new drive I'd have been fine, but because it was daisychained I screwed myself? Addit'l drive did appear, but only as standalone.



Am downloading 9.1 now...

[Ken_Putnam]

If you can still find an LEO on Ebay or another Auction site, you may be able to leave both libraries connected.

(Veritas does not sell any v9 serials anymore, AFAIK)

If you don't need both drives, remove the old one through the devices tab (before you physically disconnect it), then hook up the new one and re-run the hardware wizard. That should see that you now only have one library and instal the loader and tape drive both.

[Steve_Levine]

I've tried to remove old and add new- it still comes up as standalone- very odd.

I've since installed 9.1, but the same crap.

Windows Removeable Hardware doesn't even see the drive, though it's clearly listed in Device Manager with Veritas driver.

[tejashree_Bhate]

Hello,

Please follow the steps given in the technote below.

(title)Troubleshooting devices that are not displayed in the Devices tab or whose status appears "offline" in Backup Exec
http://support.veritas.com/docs/256134

Uninstall the OEM drivers for the medium changer.
(title) How to uninstall the Original Equipment Manufacturer driver for the medium changer in a robotic library so as to make it "Unknown medium changer

http://support.veritas.com/docs/269214

Install the latest drivers for the tape drive.

Additional Information :
For information on the recent VERITAS Backup Exec security vulnerabilities, including links to the downloads for the necessary hotfixes, please refer to the following document:
Patch summary for Security Advisories VX05-001, VX05-002, VX05-003, VX05-005, VX05-006, VX05-007

http://seer.support.veritas.com/docs/277429.htm



Note : If we do not receive your reply within two business days, this post would be marked ‘assumed answered’ and would be moved to ‘answered questions’ pool.


Thanks.

[Steve_Levine]

I've done most of this, even though it doesn't apply:

the system recognizes the tape drive just fine, not the autoloader. The device driver loaded for the loader is "unknown medium changer."

I've narrowed the issue down more:

I have basically been getting stuck because after Backup Exec is installed, the SCSIChanger device will not load at boot. It only gives an error 7000 in system log.

Thinking that it could possibly be a Windows problem, I've installed the tape drive on another server machine, running Win2003 server. Attaching the changer/drive and configuring the SCSI controller as the manufacturer specified, the server comes up fine with the "unknown medium changer" and the tape drive listed with a question mark, and unknown.

Once I install Backup Exec (and the Veritas tape driver) the system complains on boot about the SCSIChanger service.

Getting past this conflict should get me to the promised land...

[Ajit_Kulkarni]

Hello,

On what SCSI IDs you have kept the Changer and the drive of the autoloader ?

If WIndows itself is detecting the Changer as "Unknow Changer" then you need to verify the problem with it.


Regards


Additional Information :
For information on the recent VERITAS Backup Exec security vulnerabilities, including links to the downloads for the necessary hotfixes, please refer to the following document:
Patch summary for Security Advisories VX05-001, VX05-002, VX05-003, VX05-005, VX05-006, VX05-007

http://seer.support.veritas.com/docs/277429.htm



Note : If we do not receive your reply within two business days, this post would be marked ‘assumed answered’ and would be moved to ‘answered questions’ pool.