RE: Corrupt Email in Exchange 2000

[Precht, David]

Title: Message



or 
lusers

DUDE, you are 
SO NOT SUPPORTED !
-Original Message-From: 
Abercrombie, Sherry [mailto:[EMAIL PROTECTED]] Sent: Friday, May 31, 
2002 14:07To: MS-Exchange Admin IssuesSubject: RE: Corrupt 
Email in Exchange 2000

  We call them HMU's. High Maintenance Users. Of 
  course, that's when we're in a good mood, if we're not, then they might be 
  called ID10T's.
  -Original Message- From: Paul 
  Armstrong [mailto:[EMAIL PROTECTED]] 
  Sent: Friday, May 31, 2002 12:04 PM To: MS-Exchange Admin Issues Subject: RE: 
  Corrupt Email in Exchange 2000 
  Personally, I dont care about using Brick Level Backup 
  and I know what you mean about BE being extremely sensitive. BackupExec can 
  skip a file and it will say your backup failed. Unless you look at the log and 
  see that it was one error that wasnt important which caused the backup to fail 
  but in actuality it backed up everything. The problem is the setup is at a 
  place I consult at, so I am not there all the time. So the person who changes 
  the tapes, see backup failed, and calls me whining "My Backup's not working, 
  WAAHAHH!!!". So I tell him to check the log before calling me and see if it 
  was critical or not. But ofcourse he's lazy and doesn't care he just doesn't 
  want to see anything negative. So instead of fighting it, I will disable the 
  brick level and rely on the file  mail rentention option within E2K. I 
  swaer some users are babies and expect everything to work perfectly all of the 
  time!
   -Original 
  Message-  From: Abercrombie, Sherry [mailto:[EMAIL PROTECTED]] 
   Sent: Fri 
  5/31/2002 12:53 PM  To: MS-Exchange Admin Issues 
   Cc: 
   Subject: 
  RE: Corrupt Email in Exchange 2000 
   
   
   I've seen the same 
  thing with Backup Exec 8.6 on an Exchange 5.5 server doing mailbox 
  backups. Personally I think it's just one of those "features" of BE 
  8.6. On regular data backups, even with Remote Agent  Open Files 
  Options Agent installed I've seen the backup hit an open file, report that it 
  is corrupt, back it up or not, and report the backup job as failed, although 
  everything thing else backed up successfully. 
   -Original 
  Message-  From: Paul Armstrong [mailto:[EMAIL PROTECTED]] 
   Sent: 
  Friday, May 31, 2002 11:41 AM 
   To: 
  MS-Exchange Admin Issues  
  Subject: RE: Corrupt Email in Exchange 2000 
   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

Corrupt Email in Exchange 2000

[Paul Armstrong]

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?!?!?
ŠËB…ªíz¶§tPjØm¶ŸÿÃ,ºvޖÛ(~Ü­ç(›÷±r§éb²×!j»^®f

Re: Corrupt Email in Exchange 2000

[Missy Koslosky]

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

Re: Corrupt Email in Exchange 2000

[Missy Koslosky]

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






List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm

Re: Corrupt Email in Exchange 2000

[Missy Koslosky]

ooohhh...  stop, you're hurting my feelings.

It's certainly a known issue.  Brick level backups fire errors all of
the time.  It's the nature of the beast.   There are other, better ways
to recover from mistakenly deleted items.  Especially in E2K.

- Original Message -
From: Joe Irvine [EMAIL PROTECTED]
To: MS-Exchange Admin Issues [EMAIL PROTECTED]
Sent: Friday, May 31, 2002 12:33 PM
Subject: RE: Corrupt Email in Exchange 2000


now there's an intelligent, well-thought out response.

It sounds to me like you might want to call Veritas and see if they can
help with the source of the error. it's probably a known issue.

Thanks,

Joe Irvine
Director of Information Technology
The Business Office, Inc.
(609) 597-1155, Fax (609) 597-2860
www.tbopayroll.com


-Original Message-
From: Missy Koslosky [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 31, 2002 12:15 PM
To: MS-Exchange Admin Issues
Subject: Re: Corrupt Email in Exchange 2000
Importance: Low


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

.+
 A z[ jo ˅z


List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm

RE: Corrupt Email in Exchange 2000

[Paul Armstrong]

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







.+-
«µêڝÑ@A«a¶Úÿ0²éÛz[l¡ûpj·œ¢oÞÅÈZž¥ŠË\…ªíz¸m

RE: Corrupt Email in Exchange 2000

[Joe Irvine]

now there's an intelligent, well-thought out response. 

It sounds to me like you might want to call Veritas and see if they can help with the 
source of the error. it's probably a known issue.

Thanks,

Joe Irvine
Director of Information Technology
The Business Office, Inc.
(609) 597-1155, Fax (609) 597-2860
www.tbopayroll.com


-Original Message-
From: Missy Koslosky [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 31, 2002 12:15 PM
To: MS-Exchange Admin Issues
Subject: Re: Corrupt Email in Exchange 2000
Importance: Low


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

ŠËB…ªíz¶§tPjØm¶ŸÿÃ,ºvޖÛ(~Ü­ç(›÷±r§éb²×!j»^®f

RE: Corrupt Email in Exchange 2000

[Abercrombie, Sherry]

Title: RE: Corrupt Email in Exchange 2000





I've seen the same thing with Backup Exec 8.6 on an Exchange 5.5 server doing mailbox backups. Personally I think it's just one of those features of BE 8.6. On regular data backups, even with Remote Agent  Open Files Options Agent installed I've seen the backup hit an open file, report that it is corrupt, back it up or not, and report the backup job as failed, although everything thing else backed up successfully. 

-Original Message-
From: Paul Armstrong [mailto:[EMAIL PROTECTED]] 
Sent: Friday, May 31, 2002 11:41 AM
To: MS-Exchange Admin Issues
Subject: RE: Corrupt Email in Exchange 2000



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
 
 
 
 
 
 


.+-

@A୫af0 z[lpjoZ \᥅zm



List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm

RE: Corrupt Email in Exchange 2000

[Chris Norris]

If deleted item  mailbox retention are both set to 30 days and the backup rotation is 
30 days what is the point of brick level backups?  Correct me if I am wrong but with 
those two settings and a little education the Big Boss should be able to recover his 
own deleted item and not have to wait for you to do a restore from tape...


-Original Message-
From: Paul Armstrong [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 31, 2002 12:41 PM
To: MS-Exchange Admin Issues
Subject: RE: Corrupt Email in Exchange 2000


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

RE: Corrupt Email in Exchange 2000

[Paul Armstrong]

Personally,  I dont care about using Brick Level Backup and I know what you mean about 
BE being extremely sensitive. BackupExec can skip a file and it will say your backup 
failed. Unless you look at the log and see that it was one error that wasnt important 
which caused the backup to fail but in actuality it backed up everything. The problem 
is the setup is at a place I consult at, so I am not there all the time. So the person 
who changes the tapes, see backup failed, and calls me whining My Backup's not 
working, WAAHAHH!!!. So I tell him to check the log before calling me and see if it 
was critical or not. But ofcourse he's lazy and doesn't care he just doesn't want to 
see anything negative. So instead of fighting it, I will disable the brick level and 
rely on the file  mail rentention option within E2K. I swaer some users are babies 
and expect everything to work perfectly all of the time!

-Original Message- 
From: Abercrombie, Sherry [mailto:[EMAIL PROTECTED]] 
Sent: Fri 5/31/2002 12:53 PM 
To: MS-Exchange Admin Issues 
Cc: 
Subject: RE: Corrupt Email in Exchange 2000



I've seen the same thing with Backup Exec 8.6 on an Exchange 5.5 server doing 
mailbox backups.  Personally I think it's just one of those features of BE 8.6.  On 
regular data backups, even with Remote Agent  Open Files Options Agent installed I've 
seen the backup hit an open file, report that it is corrupt, back it up or not, and 
report the backup job as failed, although everything thing else backed up 
successfully.  

-Original Message- 
From: Paul Armstrong [mailto:[EMAIL PROTECTED]] 
Sent: Friday, May 31, 2002 11:41 AM 
To: MS-Exchange Admin Issues 
Subject: RE: Corrupt Email in Exchange 2000 


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

RE: Corrupt Email in Exchange 2000

[Andy David]

Not to be a pendant, but if a file is simply skipped, the job does not show
up as failed in BE.
It fails if BE thinks its corrupt, or doesnt have permissions to the file
etc. etc.., the job fails.
I do agree however, that a job status of incomplete would be more
descriptive and probably cause less heartache.




-Original Message-
From: Paul Armstrong [mailto:[EMAIL PROTECTED]] 
Sent: Friday, May 31, 2002 1:04 PM
To: MS-Exchange Admin Issues
Subject: RE: Corrupt Email in Exchange 2000


Personally,  I dont care about using Brick Level Backup and I know what you
mean about BE being extremely sensitive. BackupExec can skip a file and it
will say your backup failed. Unless you look at the log and see that it was
one error that wasnt important which caused the backup to fail but in
actuality it backed up everything. The problem is the setup is at a place I
consult at, so I am not there all the time. So the person who changes the
tapes, see backup failed, and calls me whining My Backup's not working,
WAAHAHH!!!. So I tell him to check the log before calling me and see if it
was critical or not. But ofcourse he's lazy and doesn't care he just doesn't
want to see anything negative. So instead of fighting it, I will disable the
brick level and rely on the file  mail rentention option within E2K. I
swaer some users are babies and expect everything to work perfectly all of
the time!

-Original Message- 
From: Abercrombie, Sherry [mailto:[EMAIL PROTECTED]] 
Sent: Fri 5/31/2002 12:53 PM 
To: MS-Exchange Admin Issues 
Cc: 
Subject: RE: Corrupt Email in Exchange 2000



I've seen the same thing with Backup Exec 8.6 on an Exchange 5.5
server doing mailbox backups.  Personally I think it's just one of those
features of BE 8.6.  On regular data backups, even with Remote Agent 
Open Files Options Agent installed I've seen the backup hit an open file,
report that it is corrupt, back it up or not, and report the backup job as
failed, although everything thing else backed up successfully.  

-Original Message- 
From: Paul Armstrong [mailto:[EMAIL PROTECTED]] 
Sent: Friday, May 31, 2002 11:41 AM 
To: MS-Exchange Admin Issues 
Subject: RE: Corrupt Email in Exchange 2000 


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

RE: Corrupt Email in Exchange 2000

[Kevin Miller]

Have you tested those backups?

--Kevinm KMAP-SR, M, WLKMMAS, UCC+WCA, And Beyond
http://www.daughtry.ca/ For Graphics and WebDesign, GO here!


-Original Message-
From: Paul Armstrong [mailto:[EMAIL PROTECTED]] 
Sent: Friday, May 31, 2002 9:41 AM
To: MS-Exchange Admin Issues
Subject: RE: Corrupt Email in Exchange 2000


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







.+-
 @Aѫa 0 z[lpjo  Z \˅zm


List Charter and FAQ at:
http

RE: Corrupt Email in Exchange 2000

[Eldridge, Dave]

I agree just because be reports a backup failed doesn't mean that you got a
bad backup. Just have the log emailed to you and it takes just seconds to
determine if it was really a fatal failed backup or not.

dave

-Original Message-
From: Paul Armstrong [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 31, 2002 11:04 AM
To: MS-Exchange Admin Issues
Subject: RE: Corrupt Email in Exchange 2000


Personally,  I dont care about using Brick Level Backup and I know what you
mean about BE being extremely sensitive. BackupExec can skip a file and it
will say your backup failed. Unless you look at the log and see that it was
one error that wasnt important which caused the backup to fail but in
actuality it backed up everything. The problem is the setup is at a place I
consult at, so I am not there all the time. So the person who changes the
tapes, see backup failed, and calls me whining My Backup's not working,
WAAHAHH!!!. So I tell him to check the log before calling me and see if it
was critical or not. But ofcourse he's lazy and doesn't care he just doesn't
want to see anything negative. So instead of fighting it, I will disable the
brick level and rely on the file  mail rentention option within E2K. I
swaer some users are babies and expect everything to work perfectly all of
the time!

-Original Message- 
From: Abercrombie, Sherry [mailto:[EMAIL PROTECTED]] 
Sent: Fri 5/31/2002 12:53 PM 
To: MS-Exchange Admin Issues 
Cc: 
Subject: RE: Corrupt Email in Exchange 2000



I've seen the same thing with Backup Exec 8.6 on an Exchange 5.5
server doing mailbox backups.  Personally I think it's just one of those
features of BE 8.6.  On regular data backups, even with Remote Agent 
Open Files Options Agent installed I've seen the backup hit an open file,
report that it is corrupt, back it up or not, and report the backup job as
failed, although everything thing else backed up successfully.  

-Original Message- 
From: Paul Armstrong [mailto:[EMAIL PROTECTED]] 
Sent: Friday, May 31, 2002 11:41 AM 
To: MS-Exchange Admin Issues 
Subject: RE: Corrupt Email in Exchange 2000 


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

RE: Corrupt Email in Exchange 2000

[Andy David]

How many times have you needed to restore a mailbox using this system?


-Original Message-
From: Paul Armstrong [mailto:[EMAIL PROTECTED]] 
Sent: Friday, May 31, 2002 12:41 PM
To: MS-Exchange Admin Issues
Subject: RE: Corrupt Email in Exchange 2000


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







.+-

@A୫af0  z[lpjoZ\᥅zm

--
The information contained

RE: Corrupt Email in Exchange 2000

[Abercrombie, Sherry]

Title: RE: Corrupt Email in Exchange 2000





We call them HMU's. High Maintenance Users. Of course, that's when we're in a good mood, if we're not, then they might be called ID10T's.

-Original Message-
From: Paul Armstrong [mailto:[EMAIL PROTECTED]] 
Sent: Friday, May 31, 2002 12:04 PM
To: MS-Exchange Admin Issues
Subject: RE: Corrupt Email in Exchange 2000



Personally, I dont care about using Brick Level Backup and I know what you mean about BE being extremely sensitive. BackupExec can skip a file and it will say your backup failed. Unless you look at the log and see that it was one error that wasnt important which caused the backup to fail but in actuality it backed up everything. The problem is the setup is at a place I consult at, so I am not there all the time. So the person who changes the tapes, see backup failed, and calls me whining My Backup's not working, WAAHAHH!!!. So I tell him to check the log before calling me and see if it was critical or not. But ofcourse he's lazy and doesn't care he just doesn't want to see anything negative. So instead of fighting it, I will disable the brick level and rely on the file  mail rentention option within E2K. I swaer some users are babies and expect everything to work perfectly all of the time!

 -Original Message- 
 From: Abercrombie, Sherry [mailto:[EMAIL PROTECTED]] 
 Sent: Fri 5/31/2002 12:53 PM 
 To: MS-Exchange Admin Issues 
 Cc: 
 Subject: RE: Corrupt Email in Exchange 2000
 
 


 I've seen the same thing with Backup Exec 8.6 on an Exchange 5.5 server doing mailbox backups. Personally I think it's just one of those features of BE 8.6. On regular data backups, even with Remote Agent  Open Files Options Agent installed I've seen the backup hit an open file, report that it is corrupt, back it up or not, and report the backup job as failed, although everything thing else backed up successfully. 

 -Original Message- 
 From: Paul Armstrong [mailto:[EMAIL PROTECTED]] 
 Sent: Friday, May 31, 2002 11:41 AM 
 To: MS-Exchange Admin Issues 
 Subject: RE: Corrupt Email in Exchange 2000 



 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

RE: Corrupt Email in Exchange 2000

[William Lefkovics]

That's standard. 

Sorry.



-Original Message-
From: Paul Armstrong [mailto:[EMAIL PROTECTED]] 
Sent: Friday, May 31, 2002 8:59 AM
To: MS-Exchange Admin Issues
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

RE: Corrupt Email in Exchange 2000

[Abercrombie, Sherry]

Title: RE: Corrupt Email in Exchange 2000





Can't answer for Paul, but I test my backups. Right after I received the honor of becoming the backup admin after someone left, I got bit in the butt big time because a backup system that was supposed to be backing up a couple of Novell servers went belly up apparently because of Y2K (this was in Sept. of 2000), there were no errors, backup status was showing successful, went to do a restore and there was nothing there, it was a relatively unimportant piece of data the Accounting dept. wanted, only had to do with payroll. It only took a couple of days for me to get a new backup server  software to go on it, but it sure was a painful way to get it :) 

Disaster Recovery Plan. Every good admin should have one and test test test regularly, not just once or twice a year or less.

-Original Message-
From: Kevin Miller [mailto:[EMAIL PROTECTED]] 
Sent: Friday, May 31, 2002 12:16 PM
To: MS-Exchange Admin Issues
Subject: RE: Corrupt Email in Exchange 2000



Have you tested those backups?


--Kevinm KMAP-SR, M, WLKMMAS, UCC+WCA, And Beyond http://www.daughtry.ca/ For Graphics and WebDesign, GO here!



-Original Message-
From: Paul Armstrong [mailto:[EMAIL PROTECTED]] 
Sent: Friday, May 31, 2002 9:41 AM
To: MS-Exchange Admin Issues
Subject: RE: Corrupt Email in Exchange 2000



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

Re: Corrupt Email in Exchange 2000

[Missy Koslosky]

I'm so confused.  If you know all this, why are you wasting our time
asking about it?
- Original Message -
From: Paul Armstrong [EMAIL PROTECTED]
To: MS-Exchange Admin Issues [EMAIL PROTECTED]
Sent: Friday, May 31, 2002 1:03 PM
Subject: RE: Corrupt Email in Exchange 2000


Personally,  I dont care about using Brick Level Backup and I know what
you mean about BE being extremely sensitive. BackupExec can skip a file
and it will say your backup failed. Unless you look at the log and see
that it was one error that wasnt important which caused the backup to
fail but in actuality it backed up everything. The problem is the setup
is at a place I consult at, so I am not there all the time. So the
person who changes the tapes, see backup failed, and calls me whining
My Backup's not working, WAAHAHH!!!. So I tell him to check the log
before calling me and see if it was critical or not. But ofcourse he's
lazy and doesn't care he just doesn't want to see anything negative. So
instead of fighting it, I will disable the brick level and rely on the
file  mail rentention option within E2K. I swaer some users are babies
and expect everything to work perfectly all of the time!

-Original Message-
From: Abercrombie, Sherry [mailto:[EMAIL PROTECTED]]
Sent: Fri 5/31/2002 12:53 PM
To: MS-Exchange Admin Issues
Cc:
Subject: RE: Corrupt Email in Exchange 2000



I've seen the same thing with Backup Exec 8.6 on an Exchange 5.5 server
doing mailbox backups.  Personally I think it's just one of those
features of BE 8.6.  On regular data backups, even with Remote Agent 
Open Files Options Agent installed I've seen the backup hit an open
file, report that it is corrupt, back it up or not, and report the
backup job as failed, although everything thing else backed up
successfully.

-Original Message-
From: Paul Armstrong [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 31, 2002 11:41 AM
To: MS-Exchange Admin Issues
Subject: RE: Corrupt Email in Exchange 2000


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