Exchange Mailboxes not being backed up!

Hoping you can help me solve this problem with backing up the Exchange Mailboxes. We have several Windows 2003 servers. Backup Exec 9.1 is running on the same server as Exchange 2000 is running on. File backups run fine. However, the backup of the individual Exchange Mailboxes has always been a problem. In short, I think it has possibly never backed up anything. Recently it's been giving the message in the Job Status has been: 'Canceled, timed out'. Byte count: 0. With no job log! Veritas helpdesk has been useless.

I'm thinking it might have something to with the rights of the backup exec account. When I look at the user mailboxes the full mailbox access permission is denied for the backup exec account, although it does have read and delete rights. The backup exec account is a member of the backup operators, the domain admins and the enterprise admins. Could the problem be the fact that full access is denied? If so, how can I allow it for all mailboxes?? Please advise!!

Donovan2004Asked:
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.

Steve McCarthy, MCSE, MCSA, MCP x8, Network+, i-Net+, A+, CIWA, CCNA, FDLE FCIC, HIPAA Security OfficerIT Consultant, Network Engineer, Windows Network Administrator, VMware AdministratorCommented:
Are you running an Exchange Agent?  The agent is what allows you to backup individual mailboxes.  For a normal backup, if you are getting the information store which holds your storage groups, you are getting exchange backed up, but not at the Brick level (Individual Mailbox Level.)  

Restoring the information store will restore all mailboxes.  

Many people believe this is a better way to backup Exchange.  Set your deleted item retention to say 30 days and deleted mailbox retention to about 6 months and chances are you will never have to restore an individual mailbox, which IMHO is a pain.  Set your Veritas to backup the Information store and you are covered.  If you want the individual mailboxes, then you need the Exhange Agent.

Now, having said all of that I would do a couple of things.  If I look at the properties of my First Storage Group, my Backup Exec account is not even listed.  If yours worked previously, then I believe your Backup Exec somehow hosed itself.  I have seen this same thing many times.

How I've fixed it in the past is to fully uninstall Backup Exec and do a clean installation.  Without rebooting, I then apply all the patches.  The latest 9.1 I believe is Build 4691.1 and the patches that are applicable, and should be installed in this order, HF1, SP1, HF19, HF26, HF27 (If you have IDR), HF31, HF32 and HF33 (If you have the Exchange agent).  Lastly, load the latest Tape Device Driver file.  Once completed, then reboot your machine.

You will have to setup your backup jobs again, but this should fix your problems.

STeve
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
Donovan2004Author Commented:
Well, the Exchange Agent is installed. Backup Exec has never really worked normally for Exchange. When it *seemed* to backup the mailboxes (according to the byte count at least) they had the red stripe through them in the restore view and all boxes said 0 bytes. I'd rather not apply patches right away, rebooting the server is a bit problematic...
0
Steve McCarthy, MCSE, MCSA, MCP x8, Network+, i-Net+, A+, CIWA, CCNA, FDLE FCIC, HIPAA Security OfficerIT Consultant, Network Engineer, Windows Network Administrator, VMware AdministratorCommented:
I'd say you are at quite a dilemma, but unfortunately to fix the problem I believe you are going to have to take some decisive measures.  With what you described, I would uninstall the old version, put on the new and piggback all those patches to get the installation all in 1 reboot.  I just rebuilt 2 servers yesterday using this exact procedure.  At least it minimized the rebooting on the installation.  If you have a problematic server on reboots, then perhaps there are more issues and thus it is even more critical to get the data backed up.
0
Steve McCarthy, MCSE, MCSA, MCP x8, Network+, i-Net+, A+, CIWA, CCNA, FDLE FCIC, HIPAA Security OfficerIT Consultant, Network Engineer, Windows Network Administrator, VMware AdministratorCommented:
I will ask for the points on this one as I have put forth logical troubleshooting steps and the information necessary to lead to problem resolution
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
Storage Software

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.