SBS 2008 backup fails to back up exchange

SBSDan
SBSDan used Ask the Experts™
on
I provide support for serveral 2008sbs servers, one of which is failing to backup Exchange.  When I look at the SBS Console it reports the backup completed successfully, but when I drill down further (Server Manager>Storage>Windows Server Backups) I see "completed with warnings".  "Application will not be available for recovery from this backup".  I also see exchange log files have not been flushed since this started.  Looking back to mid December when this started, I noticed the backup was changed from 1x to 3x a day (a precaution due to a problem with the RAID that has since been resolved).  Exchange email is working but logs are not purging.  I am seeing a lot of post to disable circular logging, but this is already disabled.

I upgraded Exchange to sp3, and backups still fail.  In the event viewer I get Event ID 565 "consistancy check for component 'long string of alphanumeric'\'microsoft exchange server\microsoft information store'server name' failed.  Application Exchange' will not be available in the backup done at time ""  Help!
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®

Commented:
best bet is to use eseutil to check for errors in the database files

Commented:
I think you have a problem with your Exchange log files.

Have a look at this:

http://www.msexchange.org/articles/Exchange-log-disk-full.html

Skip down to: The path less traveled- Remove unneeded log files manually

Commented:
You should do a microsoft backup to commit the log files before you do anything else

Author

Commented:
Hi all, sorry for the long delay on getting back to this.  The problem still exists, logs have accumulated since mid december.  The built in 2008SBS backup completes successfully except for Exchange.

I ran eseutil /mh and it showed
Initiating FILE DUMP mode...
         Database: E:\Program Files\Microsoft\Exchange Server\Mailbox\First Stor
age Group/mailbox database.edb

        File Type: Database
   Format ulMagic: 0x89abcdef
   Engine ulMagic: 0x89abcdef
 Format ulVersion: 0x620,12
 Engine ulVersion: 0x620,12
Created ulVersion: 0x620,12
     DB Signature: Create time:01/27/2010 11:29:39 Rand:2967239 Computer:
         cbDbPage: 8192
           dbtime: 261603286 (0xf97bfd6)
            State: Clean Shutdown
     Log Required: 0-0 (0x0-0x0)
    Log Committed: 0-0 (0x0-0x0)
   Streaming File: No
         Shadowed: Yes
       Last Objid: 20151
     Scrub Dbtime: 0 (0x0)
       Scrub Date: 00/00/1900 00:00:00
     Repair Count: 0
      Repair Date: 00/00/1900 00:00:00
 Old Repair Count: 0
  Last Consistent: (0xFE29,C5,1B)  02/02/2011 18:08:54
      Last Attach: (0xFD2E,9,86)  01/31/2011 17:05:45
      Last Detach: (0xFE29,C5,1B)  02/02/2011 18:08:54
             Dbid: 1
    Log Signature: Create time:01/27/2010 11:29:39 Rand:2955862 Computer:
       OS Version: (6.0.6002 SP 2 NLS 500100.50100)

Previous Full Backup:
        Log Gen: 58984-58985 (0xe668-0xe669) - OSSnapshot
           Mark: (0xE66A,8,16)
           Mark: 12/13/2010 23:00:57

Previous Incremental Backup:
        Log Gen: 0-0 (0x0-0x0)
           Mark: (0x0,0,0)
           Mark: 00/00/1900 00:00:00

Previous Copy Backup:
        Log Gen: 0-0 (0x0-0x0)
           Mark: (0x0,0,0)
           Mark: 00/00/1900 00:00:00

Previous Differential Backup:
        Log Gen: 0-0 (0x0-0x0)
           Mark: (0x0,0,0)
           Mark: 00/00/1900 00:00:00

Current Full Backup:
        Log Gen: 0-0 (0x0-0x0)
           Mark: (0x0,0,0)
           Mark: 00/00/1900 00:00:00

Current Shadow copy backup:
        Log Gen: 0-0 (0x0-0x0)
           Mark: (0x0,0,0)
           Mark: 00/00/1900 00:00:00

     cpgUpgrade55Format: 0
    cpgUpgradeFreePages: 0
cpgUpgradeSpaceMapPages: 0

       ECC Fix Success Count: none
   Old ECC Fix Success Count: none
         ECC Fix Error Count: none
     Old ECC Fix Error Count: none
    Bad Checksum Error Count: found (119)
Last Bad Checksum Error Date: 02/02/2011 01:00:57
Old bad Checksum Error Count: none

Operation completed successfully in 1.825 seconds.

Any thoughts?  Should I just reinitialize the backup job so it gets a fresh new backkup?

Author

Commented:
Actually this issue is still open, has not been resolved.  No experts responded to my last response... I have since created a VM of this server and would like some more help with this issue... SBDan
Awarded 2009
Top Expert 2010

Commented:
working with author
Awarded 2009
Top Expert 2010
Commented:
the first thing I would do would be to enable circular logging to flush the logs, it's possible a corrupt log is preventing the backup.

Once that is done, re-enable it.

Then go through the backup wizard again and re-create the jobs.

Author

Commented:
So all the current logs are committed?  I worry about loosing emails if I flush the logs via 'circular logging', as of now I have all the logs (as far as I can see).
Awarded 2009
Top Expert 2010

Commented:
yes they are all commited.  They get put in to a transaction log so that you can recover them after restoring the last full backup, this is why they always recommend you keep the logs on a seperate disk.

Author

Commented:
OK I will make an offline backup of Exchange this weekend and then turn on circular logging long enough to flush, then turn it back off.  I will know by next week if the backup is flushing the logs OK.

Author

Commented:
OK, so I dismounted and did a backup, then enabled circular logging and mounted.  I then dismounted and mounted, so all the logs cleared.  Now I do a backup and get the following in the event viewer with the same failed backup message:
 MSExchangeIS (2364) First Storage Group: The database page read from the file "E:\Program Files\Microsoft\Exchange Server\Mailbox\First Storage Group\Mailbox Database.edb" at offset 16014213120 (0x00000003ba858000) (database page 1954859 (0x1DD42B)) for 8192 (0x00002000) bytes failed verification due to a page checksum mismatch.  The expected checksum was 5159515053027925494 (0x479a479abd029df6) ...
Awarded 2009
Top Expert 2010
Commented:
OK, looks like there could be some problems with the store.

As it's SBS2008 create a new mailbox store, mI've all the mailboxes then delete the original store, making a note of the name.

Then re-create the store with the same name and move the mailboxes back, then delete the temporary store you created.this will give you an error free store

Author

Commented:
From what I'm reading online the deleted items cache will be emptied for all users?  I will need to let them know to check their deleted items for anything important prior to performing this.
Awarded 2009
Top Expert 2010
Commented:
The dumpster will be cleared, they won't really know about this unless they have deleted something out of their deleted items.
Awarded 2009
Top Expert 2010

Commented:
This question has been classified as abandoned and is being closed as part of the Cleanup Program. See my comment at the end of the question for more details.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial