I'm having a few issues backing up my Exchange 2010 Mailbox file. The first message I have is the most disconcerting: "The application will not be available for recovery from this backup. The consistency check failed for the component Microsoft Exchange Server\Microsoft Information Store\<Mail Server>\<GUID>. Contact the application vendor to resolve this issue." The database backs up to the specified file location, but running a BPA scan says it's never been backed up before. It seems this is also the reason the log files aren't being deleted after backup. I'm bumping up on 80GB of log files on a 200 GB partition and we're starting to run low on room. I ran an ESEUTIL command on our database and it's working perfectly, no corruptions. I've seen several articles answer questions somewhat related to this, but none seem to answer it completely. We're running this on Server 2008 R2, x64. This hosts all roles for the Exchange Server - Client Access, Hub Transport, and Mailbox. ----------- Ron E Biggs Network Administrator Entertainment Studios

consistency should be checked with isinteg, not eseutil /g. Isinteg is Exchange aware, while eseutil just verifys the Database without any Exchange awareness.

yes but isinteg is no longer supported under Exchange 2010. When you try to mount the database a consisty check is done. If you want to run a consisty check on a monted database please use new-mailboxrepair request. Some more inforamtion you will find on http://msexchangeteam.com/archive/2010/08/23/455899.aspxregards Thomas Paetzold visit my blog on: http://sus42.wordpress.com

Yeah this new-mailbox repair request seems the way to go, except I don't see it in my shell scripts directory (I'm assuming it's a script I run in the EMS). Do I need to download it from somewhere?----------- Ron E Biggs Network Administrator Entertainment Studios

Ok, well this wound up being a call to Microsoft. First off, it's true we needed to back up to a local drive. So I took care of that. But there were also inconsistencies that the backup couldn't detect. So the Microsoft guy performed these steps, to back up through the VSS SDK and do a backup successfully: = Installed Vss sdk 7.2 = Created a components.txt file = Ran the below command to take the backup BETEST.exe /B /E /T 1 /S output.XML /C components.txt /D F:\betest > output.txt Subsequent standard backups have all been successful.----------- Ron E Biggs Network Administrator Entertainment Studios

I have the exact same issue, this Windows Server Backup error "The application will not be available for recovery" for Exchange 2010, and because of this the log files are not being truncated. "Application will not be available for recover from this backup. Consistency check failed for component Microsoft Exchange Server\Microsoft Information Store\ServerName\GUID. Contact the vendor for help in resolving." However, the suggestion above did not have any effect for me. Subsequent backups still fail with the same error. Is there any other resolution for this issue?

Yes, I personally have found third party a better solution as you can also backup to NAS if needed. Windows 2008 backup will not let you do this. I would suggest BackupAssist as it basically sits on top of Windows 2008 but allows you all the features and functions 2008 backup is missing, e.g. email notification, etc.. Its fairly inexpensive at $249 for full product.MVP Exchange Server

Thanks for the info. I'd rather use the integrated tools and have them function as advertised, though. Or is it just hopelessly non-functional?

It's not hopeless. Once we fixed this issue it's been backing up safely, daily, reliably, for months. Here's the fuller resolution according to our Microsoft rep: RESOLUTION =========== The following steps helped to resolve the issue = Windows server backup complete successfully with below warning "Consistency check failed for application exchange" = we had only Two volume X drive contains system files Y drive contains Exchange database Note : Windows Server backup occur at the volume level. This means that all data on a particular volume will be backed up. For instance, in my test environment, I had more than one database (DB) or storage group (SG) stored together on the same LUN, both SGs or DBs will be backed up in this case. You cannot select to only backup one SG or DB stored on a LUN with multiple SGs or DBs present = We shrink the Y drive and created a new volume Z drive = Installed Vss sdk 7.2 = Created a components.txt file = Ran the below command to take the backup BETEST.exe /B /E /T 1 /S output.XML /C components.txt /D Z:\betest > output.txt = Backup completed successfully and it purged the log files = We tried to take the backup using Windows Server backup and this time the backup completed successfully This is how we resolved this issue RELATED DOCUMETS ===================== Changes to Backup and Restore in Exchange 2010 http://msdn.microsoft.com/en-us/library/dd877018.aspx Understanding Backup, Restore and Disaster Recovery http://technet.microsoft.com/en-us/library/dd876874.aspx Uncovering the new Exchange 2010 Volume Snapshot (VSS) Plug-in (Part 1) http://www.msexchange.org/articles_tutorials/exchange-server-2010/high-availability-recovery/uncovering-new-exchange-2010-volume-snapshot-vss-plug-in-part1.html ----------- Ron E Biggs Network Administrator Entertainment Studios