Enable and test datacenter switchovers. This will guide you:
You have to enable DAC mode for this to work smoothly:
https://learn.microsoft.com/en-us/exchange/high-availability/database-availability-groups/dac-mode?view=exchserver-2019
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi all,
I am currently testing our desaster scenario and try to make a documentation.
Scenario:
One DAG containing 3 databases (2x Exchange 2016 on site, 1x Exchange 2016 in Datacenter)
Exch01 (on site) holds DB01 and DB02, Exch03 (on site) holds DB03.
Exch02 located in the datacenter holds a DB copy of all DBs
In case of desaster (fire, war, bombing the city, etc), the on site hardware is lost and we want to keep services up using the hardware in the datacenter.
As 2/3 servers are shut down abruptly, the DAG will not shift the active mount to the datacenter and additional the quorum of the DAG is lost.
Now the race begins:
At the current point I cannot find the correct way how to start.
Having two exchange in both sites would result in a FW witness that either sits on site or in the datacenter and whenever the WAN is gone, our DAG would unmount the DBs -> no solution.
Looking forward to any answer that may guide me to the correct startpoint.
Brgds, Niclas
Enable and test datacenter switchovers. This will guide you:
You have to enable DAC mode for this to work smoothly:
https://learn.microsoft.com/en-us/exchange/high-availability/database-availability-groups/dac-mode?view=exchserver-2019
Hi again,
I resintalled the test lab.
Once two Exch are powered off (that had the acive DB copy), the remaining one does not get active.
As DAC is enabled, I then try to mark the stop the DAG fpr the failed servers, but this also does not work:
[PS] C:\Windows\system32>Stop-DatabaseAvailabilityGroup -Identity DAG -MailboxServer EXCH01
Confirm
Are you sure you want to perform this action?
Stopping mailbox server "EXCH01" in database availability group "DAG".
[Y] Yes [A] Yes to All [N] No [L] No to All [?] Help (default is "Y"): a
An error occurred while attempting a cluster operation. Error: Cluster API failed: "GetClusterKey() failed with 0x46.
Error: The remote server has been paused or is in the process of being started"
All servers are currently in the same AD site.
€dit: I just found my problem in not usgin the -configurationonly parameter.
With that in place I was able to fianlly shut the member down and restore the DAG with alternate FSW.
DBs were mounted automatically!
Hi,
i already read about it and alsoenabled it. During the test of stopping the DAG it also tried to connect to a failed member, thus the procedure stopped.
I assume I need to set verything up with different AD sites in order to have it working properly?
I busted my testing environment and need to reinstall everything, but will test it again afterwards.