Yeah, I am familiar with the list and it basically says that Brick Level= BAD. The 
reasoning behind this is because it takes up more space on the backup tape and makes 
your backup window larger.But if it doesn't matter that the brick level backup is 
taking up more tape space and the backup window isn't an issue then its not so bad at 
all. 
 
Like I said before, I don't rely on Brick Level as a restore method for the server but 
if the Big Boss accidently (stupidly) deletes a message or folder within his mailbox 
and wants it back and the only way to recover it is with a recent Brick Level backup, 
I dont he wants to hear that we disabled it because it took to much time. When tape 
space and backup windows become an issue this will be the first option to be disabled 
witin the backups. Also, Im not too worried about relying on the Brick Level Backup 
because I have the deleted item & mailbox retention set both to 30 days since the 
backup rotation is for 30 days, so I am covered. Oh well, thanks for the help!

        -----Original Message----- 
        From: Missy Koslosky [mailto:[EMAIL PROTECTED]] 
        Sent: Fri 5/31/2002 12:23 PM 
        To: Paul Armstrong; MS-Exchange Admin Issues 
        Cc: 
        Subject: Re: Corrupt Email in Exchange 2000
        
        

        Please keep conversations on-list.
        
        I take it  you're unfamiliar with the Exchange FAQ at
        http://www.swinc.com?
        
        ----- Original Message -----
        From: "Paul Armstrong" <[EMAIL PROTECTED]>
        To: <[EMAIL PROTECTED]>
        Sent: Friday, May 31, 2002 12:15 PM
        Subject: RE: Corrupt Email in Exchange 2000
        
        
        What do you mean by crappy backup methodology? I dont rely on individual
        mailbox backups for the server, only just in case a message or folder
        needs to be restored instead of rebuilding the whole server!
        
        -----Original Message-----
        From: Missy Koslosky [mailto:[EMAIL PROTECTED]]
        Sent: Fri 5/31/2002 12:15 PM
        To: MS-Exchange Admin Issues
        Cc:
        Subject: Re: Corrupt Email in Exchange 2000
        
        
        
        This isn't corrupt information.  It's crappy backup methodology.
        ----- Original Message -----
        From: "Paul Armstrong" <[EMAIL PROTECTED]>
        To: "MS-Exchange Admin Issues" <[EMAIL PROTECTED]>
        Sent: Friday, May 31, 2002 11:58 AM
        Subject: Corrupt Email in Exchange 2000
        
        
        Hello All,
        
        I am having an interesting problem with Exchange 2000 & BackupExec 8.6.
        Over the past few weeks, I have been getting errors within BackupExec8.6
        when it backs up indivdual mailboxes in Exchange 2000. There are two
        mailboxes where it finds messages that it can't access so therefore it
        skips it. One of the messages is as follows:
        Unable to open the item Howard Perl [howardp]?Top of Information
        Store?Inbox?read?oldham?LEXINGTON PO#57016699 - skipped.
        Access denied to file ?Howard Perl [howardp]?Top of Information
        Store?Inbox?read?oldham?LEXINGTON PO#57016699.
        
        This happens on a dozen or so emails within two mailboxes but none of
        the others. Both of these mailboxes belong to users of RIM Blackberry's.
        This is the only thing that I can see that can be causing the problem.
        Anyway, when I got into the mailbox and drill down to the exact message
        that it is skiiping, I can't even open it within Outlook (this is both
        as the user and as Administrator).
        
        The first time to problem came up, I just deleted the messages that
        Outlook said couldn't access or was corrupt and the problem went away
        for a few days but now its back. I search on Technet for corrupt
        messages and find nothing but articles on corrupt stores and mta, etc.
        Has anybody seen this happen before and found a solution? I called
        Veritas tech Support and the basically say that if outlook can't open
        the message then it has to do with Exchange2k and not backupexec. The
        Exchange server is running W2KSP2 and E2KSP2, it is also running Trend
        Scanmail and Norton AntiVirus Corp Edition. BackupExec is on another
        server and the remote agent is installed on the mail server. Any
        ideas?!?!?
        .+
        A z[ jo ˅z
        
        
        List Charter and FAQ at:
        http://www.sunbelt-software.com/exchange_list_charter.htm
        
        
        
        
        
        

.+-
ڝ@Aa0z[lpjoZ\zm


Reply via email to