Backup Exec 9.1 w/ Rem B2D issue

I have a server (Win Server 2003 standard) with an Iomega Rev35 drive in, running Veritas BEWS 9.1.  It's worked just fine for over a year, but recently, i've run into a situation that is specifically documented in Symantec's knowledgebase, but their resolution isn't working.  The problem is the job never fires off.  At the sheduled time, it starts, but instead of going into a "running" state, the status stays "Queued", and the job must be cancelled.  Symantec seems to indicate that this is the result of a lock file (.lck) not getting cleared after a prior backup.  In my situation, however, this is not the case.  There is no lock file present on any of my media when the backup starts.  I've found that deleting the removable backup to disk device from the devices tab, and re-creating it works for a few days, but the issue resumes after that.

Anybody run into this?
logicaltechsAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

novaspoonmanCommented:
Is the Removable Storage service running?

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
rindiCommented:
You may have made the media set to not be overwritable, or at least not for a certain time. Try making your media overwritable.
logicaltechsAuthor Commented:
Removable storage is running, and the media set is overwritable.

Update:  I got a good backup last night (again, after I removed and re-created the B2D device).  It will probably run fine for a few days, and then the issue will resume at some random time.
rindiCommented:
Have you checked your eventlogs for anything suspicious?
logicaltechsAuthor Commented:
Not yet, after I found out that this is a known removable B2D problem with BEWS 9.1, i've just been looking for resolution with the application.  I'll check it out.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Storage Software

From novice to tech pro — start learning today.