Exchange 2007 backup works...sometimes
I use the built-in backup program on my new SBS 2008 server, and it works about half the time these days. When it fails, I get this error in the event log: Consistency check for component 'e8ed1165-a879-49f4-8865-99a99de6a2ff'\'Microsoft Exchange Server\Microsoft Information Store\SBS-DAGAZ' failed. Application 'Exchange' will not be avaliable in the backup done at time '12/21/2009 9:00:17 PM' Here's the backup batch file: wbadmin start backup -include:C:,D: -backuptarget:F: -allcritical -vssFull -quiet I see no reason why it should work some nights, but not others. Any ideas?
December 24th, 2009 12:43am

Any potential overlap in your maintenance schedule?
Free Windows Admin Tool Kit Click here and download it now
December 24th, 2009 12:45am

Hi,Please try to check the backup event log to see if any other related error event has been logged there.Introducing SBS 2008 Backuphttp://blogs.technet.com/sbs/archive/2008/11/03/introducing-sbs-2008-backup.aspxBesides,I recommend you to post the issue in newsgroup for SBS to get relevant help.http://technet.microsoft.com/en-us/sbs/bb676723.aspxRegards,Xiu
December 25th, 2009 10:32am

I checked the (enormous) list of built-in scheduled tasks, and the only one that looked like it might overlap with my backup was the "Consolidator" task, which has something to do with the Customer Service Improvement Program. Not terribly important sounding, so I'll disable that and see if my backup runs better.
Free Windows Admin Tool Kit Click here and download it now
December 30th, 2009 9:03pm

No errors in the event log before the backup fails, but here are some Information events that might be related, just before the backup failure: Event 300, ESENT: lsass (676) The database engine is initiating recovery steps. ________ Event 301, ESENT: lsass (676) The database engine has begun replaying logfile \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy127\Windows\ntds\edb.log. ________ Event 302, ESENT: lsass (676) The database engine has successfully completed recovery steps. ________ Event 103, ESENT: lsass (676) The database engine stopped the instance (1). ________ Event 0, esbexchange: The description for Event ID 0 from source wsbexchange cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: Service started _________ Does any of that look relevant? I couldn't find any help in the links you provided...
December 30th, 2009 9:10pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics