• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 231
  • Last Modified:

Exchange permission error on SBS 2003 running Exchange 2003

I'm troubleshooting a BackupExec error that is related to Exchange. Here's the error message:

(Server: "SVSERVER") (Job: "Exch MB Fri") Exch MB Fri -- The job failed with the following error: Access is denied.


Any clues as to where in Exchange I need to look to resolve this problem? It appeas to be a permission-based error obviously. Thanks!
0
WineGeek
Asked:
WineGeek
  • 3
  • 3
1 Solution
 
SembeeCommented:
Are you doing mailbox backups or information store backups?

On the basis of your question, there isn't much more to go on.

Simon.
0
 
WineGeekAuthor Commented:
You're right, I was in a big hurry when I wrote this. This is a brand new network for me, I'm taking it over from another admin whom I am supposed to meet with next week to do a hand-off... as a little context for my questions. He was supposedly an ex-Navy security expert and he went crazy with configuring Special Permissions and specifically Deny permissions all over the place. Never seen a server locked down like this one.

Anyway, This particular backup job that is erroring is only backing up the Microsoft Exchange Mailboxes and the Microsoft Exchange Public Folders. The backup job is defined in BackupExec. So I looked at the NTFS permissions for the Admin group; I checked the permissions on the properties of the Exchange server object in ESM, and I also checked them on the MDBDATA folder. The Admin group did not have Full Control so I gave it to them and we'll see what happens this Friday when that Friday only job runs again.

Any thoughts?
0
 
SembeeCommented:
Oh dear, someone who knows better than Microsoft on how to set security permissions. You will probably be chasing your tail forever on that one as nothing will work correctly.

If it is mailbox backup as opposed to information store backup then I wouldn't be surprised if you will get errors. Mailbox (aka brick level) backups will always generate errors.

Simon.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
WineGeekAuthor Commented:
Great. Thank you for that insight though. So I should have it backing up the mailbox store and make sure it' not backing up at the mailbox level? What's the difference in your opinion?
0
 
SembeeCommented:
Backing up the information store is the only way to do a backup that Exchange considers to be a backup.
If you are using Veritas Backup Exec, then make sure that JUST the information store is selecting - not the mailboxes and not the public folders.

The difference is that mailbox backups are slow, inefficient, useless in most scenarios (including disaster recovery). They are also error prone and simply pointless. On Exchange 2003 if you need to restore a mailbox then simply using the recovery storage group. By setting deleted item retention and other options inside Exchange having to use backups shouldn't be required outside of DR. I know of Exchange admins who have never had to do restores, and outside of DR and testing I have only had to restore data perhaps a dozen times.

Simon.
0
 
WineGeekAuthor Commented:
Good info and in generally line with my experience. It's definitiely backing up at the mailbox and Public Folder levels and there are errors galore in the job summary in BackupExec. So I'll edit that backup job to where it's backing up at the information store level and go from there. Thanks!
0
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.

Join & Write a Comment

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now