• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 517
  • Last Modified:

Windows server backup util when backing up Exchange 2010 sp1

We have some issues without 3rd party backup app. so now we have reverted to good old windows backup. But now we are getting a weird error when trying to back up the store:

The application will not be available for recovery from this backup. The consistency check failed for the component Microsoft Exchange Server\Microsoft Information Store\%servername%\%some funny code/numbers%

Is this backup we have made invalid? How can I find out what the issues are with exchange to that we can get a valid backup made and get the logs truncated. Please advise
0
ablsysadmin
Asked:
ablsysadmin
  • 4
  • 2
1 Solution
 
Raheman M. AbdulCommented:
You need to perform full backup again and test
0
 
Raheman M. AbdulCommented:
Follow the steps in: http://technet.microsoft.com/en-us/library/dd876851.aspx

You need to change the registry keys as given in the link above.
and enable the circular logging on databases
0
 
ablsysadminAuthor Commented:
hi, we use DAG's and DAG's and circular logging dont like eachother.

So what you are saying is that i should drop the DAG and only run on one 'node'. then run the backup?
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
ablsysadminAuthor Commented:
ok, found this on the KB you sent:

 Using Windows Server Backup on Database Availability Group Members

If a server hosting the data being backed up is a member of a database availability group (DAG) and hosts both active and passive database copies, you must disable the Microsoft Exchange Replication service VSS writer. If the Microsoft Exchange Replication service VSS writer is enabled, the backup operation will fail.

To disable the Microsoft Exchange Replication service VSS writer, perform the following steps:

    Log on to the server by using an account that has local administrator access, and then start Registry Editor (regedit).
    Dd876851.Caution(en-us,EXCHG.141).gifCaution:
    Incorrectly editing the registry can cause serious problems that may require you to reinstall your operating system. Problems resulting from editing the registry incorrectly may not be able to be resolved. Before editing the registry, back up any valuable data.
    Navigate to HKEY_LOCAL_MACHINE\Software\Microsoft\ExchangeServer\v14\Replay\Parameters.
    Add a new DWORD value named EnableVSSWriter, and set its value to 0.
    Exit Registry Editor and then restart the Microsoft Exchange Replication service.
0
 
ablsysadminAuthor Commented:
Going to log a new call
0
 
ablsysadminAuthor Commented:
aaa
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now