StarfishTech
asked on
Exchange Backup
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?
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?
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
are they any errors reported in the event log?
ASKER
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.
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.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
what would you suggest - running isinteg?
absolutely. take a physical copy of your database and logs, then run ISINTEG as per this http://support.microsoft.c
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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
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
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.
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
Maybe your backups are struggling because your AV software is locking the EDB file for scanning everytime the backup software accesses the file
ASKER
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?
get some down time and complete a chkdsk on the storage volumes, before you do any database maintenance, or moving users.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Hi StarfishTech,
Sadly with SBS 2003, the version of exchange (standard) only allows you 1 mailbox database.
Sadly with SBS 2003, the version of exchange (standard) only allows you 1 mailbox database.