asked on The application will not be available for recovery from this backup (Windows Server Backup)
Hi guys!!
I have a big issue with my Email server!!! The situation is like this:
I have 2 windows server 2008 R2 servers...... One has Exchange server 2010 and the other one is acting as a back up for the Active Directory and Domain controller. I backup the first server and the Exchange 2010 mailboxes with Windows Server Backup. I have had this schedule backup for almost a year and it has been working perfect until three days ago!
Three days ago I rebooted the server with the mail server because I scanned it for malware and it need to be rebooted. The second server was running when I rebooted the first one. Well, First server came back and everything was fine!! Two days after I noticed in the Windows Server Backup Status console that since that day I rebooted the first server..... the backup has been successfully finish the backups but with warnings!
The warnings say "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 first line really freaks me out because the main point of the backup is in case later on I have problems with the mailboxes or Exchange goes down I can have a backup of the Exchange and restored it. But, if I keep getting these warnings then I'm in a huge problem!!!!
I read on a post in the internet a similar example and the guy said the fallowing:
Actually, there's a real elegant solution to this for Exchange 2010 that we discovered over time. Turns out that if the server with the active database (and the backup regimen) copy gets rebooted, Exchange will move over the active copy to the other server. The other server will maintain the active copy even after the rebooted server goes back online. This results in the consistency issues which lead to a failed backup.
To avoid this, you need to make sure that the server doing the backups has the active copy of the database. If it's still giving consistency issues, switching the active DB to a backup server and then to the main one always does the trick for us.
This is the post:
http://social.technet.microsoft.com/Forums/en-US/exchangesvradminlegacy/thread/9af2afca-3e49-4fa6-ad06-5c6c50671a45/
Do think rebooting my first server crated this issue? Do you think the first server moved anything to the second server when rebooting? I have not tried any of the possible solutions I have found so far in the internet because I don't want of mess up the Database of Exchange 2010!!!
Do you have any idea of what really this problem is? Do you know a safe way to fix it and make windows backup keep backing up my server and emails without any warnings or errors?? Any help would be really appreciate it!!!
Thanks,
I have a big issue with my Email server!!! The situation is like this:
I have 2 windows server 2008 R2 servers...... One has Exchange server 2010 and the other one is acting as a back up for the Active Directory and Domain controller. I backup the first server and the Exchange 2010 mailboxes with Windows Server Backup. I have had this schedule backup for almost a year and it has been working perfect until three days ago!
Three days ago I rebooted the server with the mail server because I scanned it for malware and it need to be rebooted. The second server was running when I rebooted the first one. Well, First server came back and everything was fine!! Two days after I noticed in the Windows Server Backup Status console that since that day I rebooted the first server..... the backup has been successfully finish the backups but with warnings!
The warnings say "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 first line really freaks me out because the main point of the backup is in case later on I have problems with the mailboxes or Exchange goes down I can have a backup of the Exchange and restored it. But, if I keep getting these warnings then I'm in a huge problem!!!!
I read on a post in the internet a similar example and the guy said the fallowing:
Actually, there's a real elegant solution to this for Exchange 2010 that we discovered over time. Turns out that if the server with the active database (and the backup regimen) copy gets rebooted, Exchange will move over the active copy to the other server. The other server will maintain the active copy even after the rebooted server goes back online. This results in the consistency issues which lead to a failed backup.
To avoid this, you need to make sure that the server doing the backups has the active copy of the database. If it's still giving consistency issues, switching the active DB to a backup server and then to the main one always does the trick for us.
This is the post:
http://social.technet.microsoft.com/Forums/en-US/exchangesvradminlegacy/thread/9af2afca-3e49-4fa6-ad06-5c6c50671a45/
Do think rebooting my first server crated this issue? Do you think the first server moved anything to the second server when rebooting? I have not tried any of the possible solutions I have found so far in the internet because I don't want of mess up the Database of Exchange 2010!!!
Do you have any idea of what really this problem is? Do you know a safe way to fix it and make windows backup keep backing up my server and emails without any warnings or errors?? Any help would be really appreciate it!!!
Thanks,
Windows Server 2008ExchangeStorage Software
Last Comment
hugonieto
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
I did have three missing log files due to the scan I did to find any malware on the server. Good thing the scan didn't delete them it just quarantine them and I was able to restore them!!