Hi all,
We have one dag with three servers accross two AD site.
Site1 : 2MBX serves
Site2: 1MBX server
Site 1 was down and we were able to swtchover to site2.
Since site1 was totally down, I have to run the following in site2
Stop-DatabaseAvailabilityGroup -Identity DAG01 -ActiveDirectorySite site1 -ConfigurationOnly
Now, site 1 is up and we need to restore service to site 1. by following
http://technet.microsoft.com/en-us/library/dd351049.aspx
Question: in site1, should I just run Start-DatabaseAvailabilityGroup or run
Start-DatabaseAvailabilityGroup -Identity DAG1 -ActiveDirectorySite site1 -ConfigurationOnly?
Which command should I run?
Thank you very much.
-----------------------------------------------------------------------------------------
1. As part of the datacenter switchover process, the Mailbox servers in the primary datacenter were put into a stopped state. When the environment (such as primary datacenter, Exchange dependencies, and wide area network (WAN) connectivity) is ready, the
first step is to put the Mailbox servers in the restored primary datacenter into a started state and incorporate them into the DAG. The way in which this is done depends on whether the DAG is in DAC mode.
a. If the DAG is in DAC mode, you can reincorporate the DAG members in the primary site by using the Start-DatabaseAvailabilityGroup cmdlet. Then, to make sure that the proper quorum model is being used by the DAG, run the Set-DatabaseAvailabilityGroup cmdlet
against the DAG without specifying any parameters.
b. If the DAG isn't in DAC mode, you can reincorporate the DAG members by using the Add-DatabaseAvailabilityGroupServer cmdlet.
2. After the Mailbox servers in the primary datacenter have been incorporated into the DAG, they will need some time to synchronize their database copies. Depending on the nature of the failure, the length of the outage, and actions taken by an administrator
during the outage, this may require reseeding the database copies. For example, if during the outage, you remove the database copies from the failed primary datacenter to allow log file truncation to occur for the surviving active copies in the second datacenter,
reseeding will be required. Each database can individually proceed from this point forward. After a replicated database copy in the primary datacenter is healthy, it can proceed to the next step.