Ntbackup errors trying to backup Exchange 2003

I am running Microsoft Exchange 2003 SP2 on a Windows Server 2003 R2 SP2. I am using NTbackup to backup Exchange to my File Server (Win 2003 Srv) where I have a Tape Drive attached. I backup the exchange server to a mapped drive on the file server where a backup is performed later that night. When running my fullbackup, sometimes the backup is successful and sometimes its not. When the back fails I get :Error: MyServer\Microsoft Information Store\First Storage Group is not a valid drive, or you do not have access. I googled this error and checked all the solutions provided and everything in my environment checks out. Microsoft admitted a bug in Ntbackup but this was supposed to have been fixed in SP1 of Server 2003. I recommended a switch to Backup Exec 11d but it got shot down due to money problems. Has anyone run into this problem before and if so, how did you resolve the issue.
DjrobluvAsked:
Who is Participating?
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.

cedarghostCommented:
Yeah, I had the exact same problems. Here was the response from Microsoft I found
Exact resolution steps depend on the nature of underlaying problem. For specified causes:
1. make sure backup media is formatted. If backup target is disk then make sure it has enough free space to accomodate all data.
2. perform full backup before trying to do incremental.
LOL, no help at all as neither of these were my issue. We ended up getting Backup Exec 11d after the server was fried and everyone lost 3 days of email........hope it doesn't happen to you. I was shot down initially on Backup Exec by the way, so at least you have covered yourself by telling the higher ups it was needed. Sometimes people have to learn the hard way.

0
LeeDerbyshireCommented:
This has just started happening to me, too.  My backup jobs had been working okay for ages, then this started happening.  The only thing I found that made a difference was to give Exchange its own, separate, backup job (I previously backed up all the drives, followed by the Exchange IS, in a single job).  It seems to work okay now, but I've still no idea what was going wrong.
0

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
DjrobluvAuthor Commented:
Thanks Lee, that seems to have resolved the issue. I wish Microsoft would revamp Ntbackup to work correctly with all their products. Seems as though this program doesn't really get too much attention at Microsoft.
0
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
Exchange

From novice to tech pro — start learning today.