Hello,


-- Do you receive any error message durning the backup?


-- Did you install the latest Drivers from Veritas?

-- Do you receive any event ids in event logs?



Thank You,

Shweta

Hi Scott,

Going through the same process you are, started last week.

I had a few problems getting this to work which were mostly driver related, I had to reinstall them a couple of times. Initially the unit showed up as a 16 slot autochanger under Robotic Libraries in BE but after a driver reinstall it showed up as Quantum 1 split into Certance 1 and 8 Slots (I'm only using the left magazine).

The other main issue I had was with the SCSI ID on the autochanger. I had to change it from 5 to 7 through the web config interface for BE to work correctly. Before this I got a "no idle devices" error message every time I asked BE to do anything.

Hope this helps,

Andy.

I'm having the same exact issue. Very frustrating when you waste a whole day trying to find out the problem. I don't really see what changing the ID should have to do with this issue , but I'll give anything a shot. I have lots of data that hasn't been protected for 2 days now while I hack at this. The drivers show up fine , I can inventory the drive , but no backups. I'm was about this close to formatting the whole machine since this was a replacement tape drive and I was starting to think the old drive left registry entries or something else to cause this issue. This may sound funny , but I'm glad to hear you had the same problem. :)

Hopefully the SCSI ID change will work.. I wonder how wide spread this issue is considering Backup exec ships with this drive.

Well, i have finally given up. i searched the internet relentlessly for a week now and have found no solution to this problem. nothing i have tried has worked. so, i am installing ARCserve 11.5 trial version to see i have the same problem. i'll report back and let you know what happens.

Thanks to everyone.

I had a similar issue installing my tape library, I believe that what I had to do after changing the LUN ID's was install the latest backup exec drivers then restart all the backup exec services (though you can just restart the box if you have that option).

Scott

I reloaded the drivers. I see no where in my drive to set the LUN ID's. Anyway I ran a backup job with a few files fine then erased all the tapes in the loader successful as well. When I go and try and run my main backup job I'm back to "No Idle Devices are Available" even though the drives remote management status says the autoloader and drive are idle.

Really starting to dislike Backup exec.

You should be able to change the IDs from both the front panel and web interfaces (termed SCSI IDs).

On web interface: Configurations - SCSI ID. Choose the ID number (I'm at 7) and "Submit".

Andy.

SCSI ID 7 is the default SCSI host adapter ID. Do not set the tape drive up to use this ID.

I thought you were referring to the LUN ID "Logical Unit Number'. You cannot alter these on this unit. Atleast I haven't seen where you can.

When you boot up the machine your SCSI card should display

SCSI ID "THE SCSI ID of the backup drive and name"
|--- Autoloader LUN 0
|--Tape drive LUN 1


with the autoloader and tape drive being the devices your are using.

If you do not see these LUN id's you probably have "Multiple LUN support" off in the SCSI host adapter.Message was edited by:
Jimi X

Just a follow up. I've got my drive working. The "Ready;No idle device ready' was actually because it thought no overwritable media was available. Even though it never actually would come up and say this.

Also the first two backups ,since I got it to work ,were 100% successful including the verify , but had a lot of soft errors. I increased the buffer size and these errors have appeared to go away.