From: Dave Goldman [MSFT] on
Brick level backups are not recommended because they copy the messages in to
the information store because:
A. Which creates a new messages and increases the information store size
B. This breaks the single instance storage schema
C. You can reintroduce corrupted items back to the mailbox
This posting is provided "AS IS" with no warranties, and confers no rights.

Download OABInteg from here:

"Bruce J" <BruceJ(a)> wrote in message
> Why are brick level backups not recommended?
> I located the error log in the sync folders but not the message itself. I
> found it, however, using the mfcmapi tool and hard deleted it.
> --
> Bruce J
> MCP, MCDST, Network+
> "Andy David {MVP}" wrote:
>> On Wed, 16 May 2007 07:49:01 -0700, Bruce J
>> <BruceJ(a)> wrote:
>> >Hi Andy,
>> >
>> >Two things make me believe it is corrupt:
>> >
>> >1) My Backup Exec software gives me an error in the log saying:
>> >
>> >WARNING: "\\SBS\Microsoft Exchange Mailboxes\****** [******]?Top of
>> >Information Store?Sync Issues1?Server Failures?Delivery Status
>> >Notification
>> >(Failure)" is a corrupt file.
>> >This file cannot verify
>> That is often a false positive when doing brick level backups - which
>> are not generally needed or recommended.
>> >
>> >2) Outlook does not synchronise properly, giving the error:
>> >
>> >The following message had an error and synchronization of it was skipped
>> >(0x800cce05)
>> Which message? Look under the Sync issues folders and see if its there
>> if you are not sure.