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

Exchange 2003 email consistancy check

Is there a way to run eseutil or isinteg on a single user email store?
If not is there another way to do it?
  • 7
  • 3
1 Solution
It is per store...
Using the Exchange tools ISINTEG and ESEUTIL to Ensure the Health of your Information Store
To start the integrity check for the PRIV1.EDB database, type the following command:
ESEUTIL /G C:\Program files\exchsrvr\mdbdata\priv1.edb

Also see:
Ramifications of running the eseutil /p or edbutil /d /r command in Exchange

Use the Eseutil.exe utility with the /mh switch to check the consistency of the public and private information stores
Description of the Isinteg utility

The Exchange Information Store service may stop responding when you run the Isinteg utility in Exchange Server 2003
Configuration Guide and Best Practices

Read the guide to learn how to orchestrate Data ONTAP, create application-consistent backups and enable fast recovery from NetApp storage snapshots. Version 9.5 also contains performance and scalability enhancements to meet the needs of the largest enterprise environments.

lanman777Author Commented:
Looks like 1.3 gig of message store. Any ideas how long it will take to run the utils?
4 gig of ram and 3gighertz processor running in the server.
Depends on what you want to do with the utils, and what drives you are using and in what RAID configuration...
a simple check shouldn't take long for you

but if you are going to run a defrag or a repair, please see this article

MS says 5-7 GB/hr; as high as 10GB/hr

Also see these articles...

How to run Eseutil on a computer without Exchange Server

Free disk space requirements for Eseutil.exe

How to defragment with the Eseutil utility (Eseutil.exe)

How to recover hard disk space from Exchange Server databases
lanman777Author Commented:
What I am trying to correct is a bunch of errors in Backup Exec 10d that just started showing up.
Here is what I am seeing in my backup logs:
These are just a few as an an example, there are a lot more. I just don't want to do more of a repair than is necessary to fix the issue.
The backup fails with these types of errors to my Exchange 2003 backup running on Windows 2003.
These just started showing up out of the blue after many months of good backup.

Backup- \\Server1\Microsoft Exchange Mailboxes
V-79-57344-33928 - Access is denied.
Weekly meeting - Kick Off Meeting.&CC calendar&Inbox&Top of Information Store&Access denied to file Don Jones [djones]
V-79-57344-33928 - Access is denied.
Company Day Celebration.&CC calendar&Inbox&Top of Information Store&Access denied to file Don Jones [djones]
V-79-57344-33928 - Access is denied.

many many more, ect.. ect..
That's a different question :-)
see this...
1. Ensure that the logon account used to connect to the Exchange mailboxes has Exchange Full Admin rights.

Set the default account in Backup Exec under Network | Logon Accounts to the account that has full rights to Exchange.

2. Ensure the mailbox is not hidden - The mailbox must be seen in the GAL (Global Address List). This can be tested by composing a new mail message in outlook and clicking the 'To:' field. Should you not see the display name in this list it is hidden.

3. The Backup Exec service account must have its own mailbox that has been tested with Outlook prior to configuring mailbox backups. If the mailbox has not had mail traffic, it can be flagged as "Inactive" by Exchange. This can be corrected by simply sending this account mail.

4. When configuring mailbox backups, always log on as the Backup Exec service account.

5. The Backup Exec service account's mailbox must be unique to the organization. No other mailbox can share the first 5 characters in common with this mailbox in the entire organization. This can be tested by composing a new mail message and then in 'To:' field type the first 5 characters of the mailbox display name, then press , this should resolve the name, if a menu pops up, then there are multiple accounts which share these first 5 characters. The matching names should be changed or the BESA mailbox name should be changed to something unique.

6. Stop and re-start the Backup Exec services after making any of the above changes. Let us know the results of the steps performed. If the issue persists, then create a new account. Give this account Domain Admin and Exchange Full Administrator rights.

In order to back up and restore individual Exchange mailboxes and public folders, use System Manager utility to grant the Exchange Administrator role to the user account at the Administrative Group level (for all Administrative Groups if there is more than one).

At Backup Exec GUI, go to Network | Logon Accounts and add the new account. Use this account to connect to the Exchange mailboxes.
go into the Inbox and delete the message . Probably that message is corrupt and causing you problems.
If you have multiple messages causing the same error, then you may have to look into doign a consistency check on the Exchange databases with eseutil and isinteg.
lanman777Author Commented:
I was hoping to just run the eseutil /g  integrity check. It came back completed successfully. I want to be thorough but do the minimal steps. If the integrity check came back successful, is there anything else I really need to run?
If you are having problems with just one mailbox, I would try moving the mailbox to a different store and try the backup again. If I still had issues with that same mailbox, I would dump the data into a pst and recreate the mailbox anew.

Featured Post

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.

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