Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

What Causes File Corrupt files?

Status
Not open for further replies.

robros

Programmer
May 22, 2001
241
US
I am now backing up each mailbox on Exchange5.5 which is running on Win2000 Advanced Server. I am using Ver8.6 of backup exec.One user who has nine corrupt files that make the backup "FAIL" I have tested the backup and I am able to restore other files from the mailboxes without issue. I am wondering what is causing just these nine files to be corrupted and if they are truly "corrupt" then how do I deal with that other then not backing up this users mailbox.

Thanks Catch Me I AM FALLING
 
Doubtful that user has 9 .pst files open.
My backups "fail" when certain SPAM messages are in the user's inbox/deleted items folders.
Veritas has a patch that helped me quite a bit:
bnt86mboxfix_250666.exe
Also, if it is SPAM (or unimportant emails) you can modify each of the job definitions' selections to NOT backup those individual emails.
my backup "fails" because of these "corrupt" SPAM messages about once a week, but after I uncheck those emails as selections I get good backups.

Trent
Network Admin
 
Hi,
As the thread mentioned by Rols rightly points out, the PST files are more than likely being accessed by the user. Maybe not even accessed, just open.
The other reason could be that the PST files are corrupt.
It has happened that when PST files approach 1 gig in size they more often than not become corrupt.
The only way to fix this is to break them up into smaller files.
Are the nine files all PST files?
 
I believe ROBROS is not refering to actual corrupt files per se (PST files) but mailbox "items"/messages, that are listed as corrupt in the mailbox backup. The mailbox backup uses the MAPI protocol transport provided by the MAPI client installed on the Backup server. So BE is actually just reporting read problems that the MAPI client itself (usually Outlook) is running into. And before anyone mentions that they can open these types of files/e-mails in Outlook just fine, consider the last time Outlook EVER reported a failure to read a message in your mailbox. It almost never does b/c it supresses all such error messages and just shows you what it can. Backup software does not have that luxury and must report all problems presented by the MAPI client for safety sake. Check out these mail items, in all likelihood they have some weird formatted attachment or the attachment has been stripped by an anti-virus program or some other mechanism. If the item seems fine, try forwarding it to another mailbox and see if it fails there too. If not, delete the original and forward it back, it could have just been that that particular placeholder (reference) in Exchange was bad.

These corrupt issues can be very time consuming, so you might want to just consider unchecking these items as suggested and simply copy and paste that section of the job log into an e-mail to that user so they can take their own actions to protect those particular e-mails or to clear them out. And if its an excessively personal e-mail for that employee then just get 'em fired, that'll fix it! (just kidding).
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top