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

Exchange 2010 DR Failback Not Working

We recently installed Exchange 2010 in our environment and ran a site DR test today.  We have DAG with 2 CAS/HUB/MBX servers at the primary site and 1 MBX server at the DR site.  The DR site is a primary for a different office and has 3 CAS/HUB/MBX servers.  The DR failover worked just as it should, we turned off the two Exchange servers at the primary site, and evicted them from the DR server.  The MBX server is on line with the alternate FSW and servicing email.  When we tried to failback, we started the 2 primary email servers and cannot start the cluster service one either server.  We get the following error when starting the cluster service:

Log Name:      System
 
Source:        Microsoft-Windows-FailoverClustering
 
Event ID:      1090
 
Task Category: Startup/Shutdown
 
Level:         Critical
 
User:          SYSTEM
 
Computer:      Exchange
 
Description:
 
The Cluster service cannot be started. An attempt to read configuration data from the Windows registry failed with error ’2'. Please use the Failover Cluster Management snap-in to ensure that this machine is a member of a cluster. If you intend to add this machine to an existing cluster use the Add Node Wizard. Alternatively, if this machine has been configured as a member of a cluster, it will be necessary to restore the missing configuration data that is necessary for the Cluster Service to identify that it is a member of a cluster. Perform a System State Restore of this machine in order to restore the configuration data.

We tried to force cleanup of the cluster from both servers and tried to start the DAG on both servers but neither is working.

Can someone please assist?
0
SRCL
Asked:
SRCL
  • 4
  • 3
1 Solution
 
Jamie McKillopIT ManagerCommented:
Hello,

Is your DAG in DAC mode? If so, did you use the Start-DatabaseAvailabilityGroup cmdlet to add the DAG members of the failed site back into the DAG? If your DAG is not in DAC mode, you need to run the Add-DatabaseAvailabilityGroupServer cmdlet.

JJ
0
 
SRCLAuthor Commented:
The DAG is in DAC Mode, used the Start-DatabaseAvailbilityGroup cmdlet and received this error:

[PS] C:\Windows\system32>Start-DatabaseAvailabilityGroup "inlsdag" -MailboxServer inlsem01
WARNING: Server 'INLSEM01' failed to be started as a member of database availability group 'INLSDAG'. Error: A
server-side database availability group administrative operation failed. Error: The operation failed. CreateCluster
errors may result from incorrectly configured static addresses. Error: An error occurred while attempting a cluster
operation. Error: Node inlsem01 is already joined to a cluster. [Server: ILNORMSMBX01.stericorp.com]
WARNING: The operation wasn't successful because an error was encountered. You may find more details in log file
"C:\ExchangeSetupLogs\DagTasks\dagtask_2013-01-26_19-24-39.387_start-databaseavailabilitygroup.log".

I get this same error with both servers.  I'm attaching the dagtask file.
dagtask-2013-01-27-00-02-43.953-.log
0
 
Jamie McKillopIT ManagerCommented:
Sounds like you did not properly terminate the DAG in the primary site before switchover. You need to run Stop-DatabaseAvailabilityGroup -Identity DAGname -ActiveDirectorySite primary site

JJ
0
Free tool for managing users' photos in Office 365

Easily upload multiple users’ photos to Office 365. Manage them with an intuitive GUI and use handy built-in cropping and resizing options. Link photos with users based on Azure AD attributes. Free tool!

 
SRCLAuthor Commented:
Thanks JJ, things are looking better.  I have both servers in the primary site stopped and the DR server is started and the databases are mounted and the email is working but the cluster service still won't start and when I try and run the start-databaseavailabilitygroup for either one of the primary servers I get "the operation wasn't successful because an error was encountered, find more details in the dagtask.....(log file attached).

Sheri
dagtask-2013-01-27-02-41-43.166-.log
0
 
Jamie McKillopIT ManagerCommented:
Try running Set-DatabaseAvailabilityGroup -identity DAGname then see if you can start the cluster service.

JJ
0
 
SRCLAuthor Commented:
Thanks for your help JJ, I contacted Microsoft and the issue was when I did the initial failover I ran the stop-databaseavailabilitygroup on each server and I should have only run it on the site.  Also I ran the configurationonly switch and I didn't need that because I still had availability to my primary DC and FSW server.  The fix was to remove the database copies from both primary servers, remove the servers from the DAG and re-add them.  I also had to run set-databaseavailabiltiygroup and change the witness server back to the primary FSW server.
0
 
SRCLAuthor Commented:
Solution provided by Microsoft
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

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