Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

Exchange permission error on SBS 2003 running Exchange 2003

Posted on 2006-06-14
6
Medium Priority
?
225 Views
Last Modified: 2010-03-06
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
Comment
Question by:WineGeek
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 3
6 Comments
 
LVL 104

Expert Comment

by:Sembee
ID: 16907901
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
 

Author Comment

by:WineGeek
ID: 16909002
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
 
LVL 104

Expert Comment

by:Sembee
ID: 16910200
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
Office 365 Training for IT Pros

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

 

Author Comment

by:WineGeek
ID: 16917365
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
 
LVL 104

Accepted Solution

by:
Sembee earned 2000 total points
ID: 16923498
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
 

Author Comment

by:WineGeek
ID: 16927435
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

Featured Post

Important Lessons on Recovering from Petya

In their most recent webinar, Skyport Systems explores ways to isolate and protect critical databases to keep the core of your company safe from harm.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article lists the top 5 free OST to PST Converter Tools. These tools save a lot of time for users when they want to convert OST to PST after their exchange server is no longer available or some other critical issue with exchange server or impor…
This article will help to fix the below errors for MS Exchange Server 2013 I. Certificate error "name on the security certificate is invalid or does not match the name of the site" II. Out of Office not working III. Make Internal URLs and Externa…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…

722 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question