Solved

Exchange Backup

Posted on 2011-02-17
13
684 Views
Last Modified: 2012-06-27
We have been having a problem backing up our exchange database on our SBS 2003 server. It has been backing up file for about 3 years now and just this week we started having problems. We back it up using Backup Exec 2010 R2 with all the latest service packs and hot fixes. The job fails and tells us that the Mailbox store is corrupt and cannot be verified. If we try to backup the database through NTBackup, we get the following error:

Backup Status
Operation: Backup
Active backup destination: File
Media name: "Exchange.bkf created 2/17/2011 at 10:03 PM"

Volume shadow copy creation: Attempt 1.
Backup of "SERVER\Microsoft Information Store\First Storage Group"
Backup set #1 on media #1
Backup description: "Set created 2/17/2011 at 10:03 PM"
Media name: "Exchange.bkf created 2/17/2011 at 10:03 PM"

Backup Type: Normal

Backup started on 2/17/2011 at 10:03 PM.
The 'Microsoft Information Store' returned 'Error returned from an ESE function call (d).

' from a call to 'HrESEBackupRead()' additional data '-'The 'Microsoft Information Store' returned 'Error returned from an ESE function call (d).

' from a call to 'HrESEBackupRead()' additional data '-'
The operation was ended.
Backup completed on 2/17/2011 at 10:07 PM.
Directories: 0
Files: 1
Bytes: 4,281,598,632
Time:  3 minutes and  23 seconds

----------------------

The operation did not successfully complete.

----------------------

Exchange is still operating completely fine and we see no kinds of errors in the system or application log. Do we really have a problem with our database?

0
Comment
Question by:StarfishTech
[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
  • 4
  • 3
  • 2
  • +3
13 Comments
 
LVL 121
ID: 34923100
are they any errors reported in the event log?
0
 

Author Comment

by:StarfishTech
ID: 34923134
That seems to be pretty clean with the exception of the following error in the application log that has surfaced twice in the last week.

Event Type:      Error
Event Source:      EXOLEDB
Event Category:      General
Event ID:      111
Date:            2/17/2011
Time:            9:39:34 PM
User:            N/A
Computer:      DHTLSERVER
Description:
Microsoft Exchange OLEDB was unable to do Schema propagation on MDB startup HRESULT = 0x80040e19.

For more information, click http://www.microsoft.com/contentredirect.asp.
0
 
LVL 6

Accepted Solution

by:
craig_j_Lawrence earned 167 total points
ID: 34923160
It is safe to say that if NTbackup is having errors reading the database, there is some type of corruption in the file.

You will need some downtime to run some integrity checks on the database
0
The Ultimate Checklist to Optimize Your Website

Websites are getting bigger and complicated by the day. Video, images, custom fonts are all great for showcasing your product/service. But the price to pay in terms of reduced page load times and ultimately, decreased sales, can lead to some difficult decisions about what to cut.

 

Author Comment

by:StarfishTech
ID: 34923172
what would you suggest - running isinteg?
0
 
LVL 6

Expert Comment

by:craig_j_Lawrence
ID: 34923230
absolutely. take a physical copy of your database and logs, then run ISINTEG as per this http://support.microsoft.com/kb/301460 article
0
 
LVL 29

Assisted Solution

by:mass2612
mass2612 earned 167 total points
ID: 34923502
Hi,

isinteg will fix logical corruption in the database. It does this by deleting internal links to records that no longer exist in the database. Therefore if you repair a database you loose data. That's why you should restore the database in preference to running a repair.

If you are going to repair you need to repair the physical corruption first (if any) with eseutil then run isinteg to fix the logical corruption. Eseutil /p deletes the damaged physical pages from the database and then eseutil /d cleans up the physical links to the damaged pages that eseutil /p deletes from the database.

I would check the physical structure of the database using eseutil /g and /k before doing a fix with isinteg and only do a repair if there were no backups available to restore from.
0
 
LVL 6

Expert Comment

by:craig_j_Lawrence
ID: 34923551
Thanks for chiming in Mass2612,

If you read the earlier posts, I suggested running CHECKs on the database. if all else fails, then restoring a previous copy of the database may be a last resort
0
 
LVL 29

Expert Comment

by:mass2612
ID: 34923614
Hi Craig - sure. Just wanted to make sure that Startfish thinks about the order of a repair. So many times I've seen people fix one or the other i.e. the physical and not logical or vice versa and then they wonder why the database keeps corrupting or giving strange behaviour.
0
 
LVL 31

Expert Comment

by:MegaNuk3
ID: 34924017
Just make sure your EDB, STM, log & chk files are excluded from file level AV scanning. You can also try disabling AV and running the NTBackup to see what happens...

Maybe your backups are struggling because your AV software is locking the EDB file for scanning everytime the backup software accesses the file
0
 

Author Comment

by:StarfishTech
ID: 34925655
I've been considering moving the users to a new database? Would that be a viable option? Is it possible in exchange 2003? Would would be the best way to go about that?
0
 
LVL 121
ID: 34925774
get some down time and complete a chkdsk on the storage volumes, before you do any database maintenance, or moving users.
0
 
LVL 17

Assisted Solution

by:lucid8
lucid8 earned 166 total points
ID: 34927816
1. Are you by chance getting a -613 in the event log as well? http://support.microsoft.com/kb/814891

2. Yes moving users to a new DB is certainly an option

3. All good suggestions above and If you upgraded AV recently its certainly worth looking at as MegaNuk3 suggested to see if that makes a difference. I have seen times where a vendor does a major update and things go south.

4. If you have a corrupt database and end up needing to do an Eseutil /P then /D and Isinteg etc be sure that AFTER you take the database offline you make a backup of the database in case things go terribly wrong.
 
0
 
LVL 6

Expert Comment

by:craig_j_Lawrence
ID: 34975492
Hi StarfishTech,

Sadly with SBS 2003, the version of exchange (standard) only allows you 1 mailbox database.
0

Featured Post

Turn Insights Into Action

You’ve already invested in ITSM tools, chat applications, automation utilities, and more. Fortify these solutions with intelligent communications so you can drive business processes forward.

With xMatters, you'll never miss a beat.

Question has a verified solution.

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

Unified and professional email signatures help maintain a consistent company brand image to the outside world. This article shows how to create an email signature in Exchange Server 2010 using a transport rule and how to overcome native limitations …
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…
In this video we show how to create an email address policy in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Mail Flow…
This video discusses moving either the default database or any database to a new volume.

719 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