e000032d consistency check of the snapshot...failed

[justhughes]

I'm getting the following error on all my incremental and full backups .I've attached a sample job log (I have removed the successful portions of the job as we have multiple datastores and only 2 seem to have had any errors in the backup). Note that two errors in the incremental backup do not show up in the failed full backup, so they may be a separate issue.

Final error: 0xe000032d - The consistency check of the snapshot for the Microsoft Exchange transaction log has failed.  You should check for possible data corruption in the transaction log that is online.
Final error category: Resource Errors

For additional information regarding this error refer to link V-79-57344-813

I've gone through all the links on the recommended link.

This link doesn't seem to provide a solution, only a workaround. http://www.symantec.com/business/support/index?page=content&id=TECH49199

This link doesn't come with the same error codes that I'm getting http://www.symantec.com/business/support/index?page=content&id=TECH135592. However I have implemented the changes just in case.

I don't have McAfee anything installed so this one doesn't seem to apply either. http://www.symantec.com/business/support/index?page=content&id=TECH162035

Is there an actual solution I can implement? Please note that I've inherited the backups and still learning about BackupExec and Exchange (by proxy).

Thank you,

Justin

[AmolB]

What is the version of Exchange?

The workaround specified in the TECH49199 is a best practice. Its always recommended NOT to use

AOFO for any database backups. Use AOFO for only flat file backups.

[justhughes]

Thanks for the quick reply.

Exchange version 2007 version 8.3.83.6

Can you give me a breakout of what the AOFO does?  I've only this week been having trouble with this error and I would guess that AOFO has been turned on this whole time (seeing as it is on now). Any idea why it only now started causing trouble?

[AmolB]

Refer to the below blog

https://www-secure.symantec.com/connect/articles/advanced-open-file-option

[justhughes]

Thanks for the blog it was an interesting read. This paragraph stood out though

In Exchange 2007, Microsoft almost stopped non-VSS backups and VSS has to be used for MS Exchange database backup. Same has happened with Windows 2008 also. So, Backup Exec always does a VSS backup with Windows 2008, even if AOFO is not enabled.

Now I should probably have mentioned that in addition to using Exchange 07, this server is on Windows 2003 SP2 and using Backup Exec 12.5. So while the second sentence doesn't apply, it does look like AOFO needs to be enabled to perform a backup of an online database. 

I was hoping to read through the best practices, but the link on the blog goes to an out-of-date location.

Do you have a link to the BEX 12 best practices? I've searched the site and can find 2010 and 11d best practices, but not for 12

[AmolB]

Refer to  http://www.symantec.com/docs/TECH83397