Prev: Exchange Server RPC Delays
Next: lostandfound object: urgent
From: Dave Goldman [MSFT] on 16 May 2007 20:04
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
etc....
--
This posting is provided "AS IS" with no warranties, and confers no rights.

Dgoldman
http://blogs.msdn.com/dgoldman
Download OABInteg from here:
http://gotdotnet.com/Community/UserSamples/Download.aspx?SampleGuid=A2338E73-F521-4071-9B1D-AAF49C346ACD


"Bruce J" <BruceJ(a)discussions.microsoft.com> wrote in message
news:0613F5E8-91B3-4B0F-A850-97B74B54B213(a)microsoft.com...
> 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)discussions.microsoft.com> 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.
>>

First  |  Prev  | 
Pages: 1 2
Prev: Exchange Server RPC Delays
Next: lostandfound object: urgent