Exchange Server 2010 datacenter switchover

What does this guide do?

Explains how to switchover a database availability group (DAG) across datacenters in Exchange 2010.

Who is it for?

Exchange 2010 administrators who help perform datacenter switchover for DAG in Exchange 2010.

How does it work?

We’ll take you through a series of steps that are specific to your situation.

Estimated time of completion:

30-60 minutes.

Welcome to the guide

Stop-DatabaseAvailabilityGroup

To start this procedure, you will use the Stop- DatabaseAvailabilityGroup cmdlet to mark a member of a database availability group (DAG) as failed, or to mark all DAG members in a specific Active Directory site as failed.

Obtain approval for datacenter switchover

Has the datacenter switchover been approved?

Before you begin the datacenter switchover, contact all those who may be affected by the switchover.

After you obtain approval by all affected parties, continue with the datacenter switchover.

Online or physically accessible DAG

Is the primary datacenter online or physically accessible?

Welcome to the guide

Stop-DatabaseAvailabilityGroup

To start this procedure, you will use the Stop- DatabaseAvailabilityGroup cmdlet to mark a member of a database availability group (DAG) as failed, or to mark all DAG members in a specific Active Directory site as failed.

Obtain approval for datacenter switchover

Has the datacenter switchover been approved?

Before you begin the datacenter switchover, contact all those who may be affected by the switchover.

After you obtain approval by all affected parties, continue with the datacenter switchover.

Online or physically accessible DAG

Is the primary datacenter online or physically accessible?

Stop-DatabaseAvailabilityGroup (Placeholder)

To start this procedure, you will use the Stop- DatabaseAvailabilityGroup cmdlet to mark a member of a database availability group (DAG) as failed, or to mark all DAG members in a specific Active Directory site as failed.

Obtain approval for datacenter switchover(Placeholder)

Has the datacenter switchover been approved?

Before you begin the datacenter switchover, contact all those who may be affected by the switchover.

After you obtain approval by all affected parties, continue with the datacenter switchover.


Online or physically accessible DAG(Placeholder)

Is the primary datacenter online or physically accessible?

Network Connectivity

Do the remote and primary datacenters have network connectivity?

Exchange Servers Online

Are the Exchange servers in the primary datacenter online?

DAG Extended

Is your DAG extended to multiple Active Directory sites?

Run the Stop-DatabaseAvailabilityGroup cmdlet in the shell

To stop the database availability group, follow these steps:

  1. On a server in the recovery datacenter, use the Exchange Management Shell to run the following command:
    Stop-DatabaseAvailabilityGroup –Identity <DAG_Name> - ActiveDirectorySite <Primary_Site>
  2. Repeat step 1 for all Active Directory sites that contain DAG members that are not in the recovery datacenter Active Directory site.

To verify that the command completed correctly, follow these steps:

  1. Verify that the servers are stopped by viewing the StartedMailboxServers and StoppedMailboxServers lists for the DAG. To do this, run the following command in the shell: Get-DatabaseAvailabilityGroup –Identity <DAG_Name>  | FL
    The StoppedMailboxServer list should show all mailbox servers in the primary datacenter and the StartedMailboxServers list should show all mailbox servers in the recovery datacenter.
  2. Verify that the cluster services on all Exchange servers that were accessible in the primary datacenter were forcibly cleaned up. To do this, follow these steps on all Exchange servers that were accessible in the primary datacenter:
    1. Start Services.msc.
    2. In the Services list, locate Cluster Service.
    3. Verify that the parameter in the Startup Type list is set to Disabled.
    4. Close Services.

If the Startup Type is not set to Disabled, forcibly clean up the cluster services and then verify the Startup Type again. To forcibly clean up the cluster services, run the following command at a Command Prompt on all accessible Exchange Servers: Cluster node /forcecleanup.

Note: If a domain controller in the primary datacenter is not available, the Stop-DatabaseAvailabilityGroup command may return an Active Directory provider error. This error can be safely ignored.


Did the Stop-DatabaseAvailabilityGroup command complete correctly?

Run the Stop-DatabaseAvailabilityGroup cmdlet in the shell

To stop the database availability group, follow these steps:

  1. On a server in the recovery datacenter, use the Exchange Management Shell to run the following command:
    Stop-DatabaseAvailabilityGroup –Identity <DAG_Name>  - MailboxServer <DAG_Member_InPrimary_Site>
  2. Repeat step 1 for all DAG members that are not in the recovery datacenter.

To verify that the command completed correctly, follow these steps:

  1. Verify that the servers are stopped by viewing the StartedMailboxServers and StoppedMailboxServers lists for the DAG. To do this, run the following command in the shell: Get-DatabaseAvailabilityGroup –Identity <DAG_Name>  | FL
    The StoppedMailboxServer list should show all mailbox servers in the primary datacenter and the StartedMailboxServers list should show all mailbox servers in the recovery datacenter.
  2. Verify that the cluster services on all Exchange servers that were accessible in the primary datacenter were forcibly cleaned up. To do this, follow these steps on all Exchange servers that were accessible in the primary datacenter:
    1. Start Services.msc.
    2. In the Services list, locate Cluster Service.
    3. Verify that the parameter in the Startup Type list is set to Disabled.
    4. Close Services.
If the Startup Type is not set to Disabled, forcibly clean up the cluster services and then verify the Startup Type again. To forcibly clean up the cluster services, run the following command at a Command Prompt on all accessible Exchange Servers: Cluster node /forcecleanup.

Note: If a domain controller in the primary datacenter is not available, the Stop-DatabaseAvailabilityGroup command may return an Active Directory provider error. This error can be safely ignored.


Did the Stop-DatabaseAvailabilityGroup command complete correctly?

DAG Extended

Is your DAG extended to multiple Active Directory sites?

Run the Stop-DatabaseAvailabilityGroup cmdlet in the shell

To stop the database availability group, follow these steps:

  1. On a server in the recovery datacenter, use the Exchange Management Shell to run the following command:
    Stop-DatabaseAvailabilityGroup –Identity <DAG_Name>  - ActiveDirectorySite <Primary_Site>-ConfigurationOnly:$True
  2. Repeat step 1 for all Active Directory sites are not the recovery datacenter.

To verify that the command completed correctly, follow these steps:

  1. Verify that the servers are stopped by viewing the StartedMailboxServers and StoppedMailboxServers lists for the DAG. To do this, run the following command in the shell: Get-DatabaseAvailabilityGroup –Identity <DAG_Name>  | FLThe StoppedMailboxServer list should show all mailbox servers in the primary datacenter and the StartedMailboxServers list should show all mailbox servers in the recovery datacenter.

Note: If a domain controller in the primary datacenter is not available, the Stop-DatabaseAvailabilityGroup command may return an Active Directory provider error. This error can be safely ignored.


Did the Stop-DatabaseAvailabilityGroup command complete correctly?

Run the Stop-DatabaseAvailabilityGroup cmdlet in the shell

To stop the database availability group, follow these steps:

  1. On a server in the recovery datacenter, use the Exchange Management Shell to run the following command:
    Stop-DatabaseAvailabilityGroup –Identity <DAG_Name > -MailboxServer <DAG_Member_In_Primary_Site >- ConfigurationOnly:$True
  2. Repeat step 1 for all DAG members that are not in the recovery datacenter.

To verify that the command completed correctly, follow these steps:

  1. Verify that the servers are stopped by viewing the StartedMailboxServers and StoppedMailboxServers lists for the DAG. To do this, run the following command in the shell: Get-DatabaseAvailabilityGroup –Identity | FL
    The StoppedMailboxServer list should show all mailbox servers in the primary datacenter and the StartedMailboxServers list should show all mailbox servers in the recovery datacenter.

Note: If a domain controller in the primary datacenter is not available, the Stop-DatabaseAvailabilityGroup command may return an Active Directory provider error. This error can be safely ignored.


Did the Stop-DatabaseAvailabilityGroup command complete correctly?

Exchange Servers Online

Are the Exchange servers in the primary datacenter online?

DAG extended to multiple Active Directory sites

Is your DAG extended to multiple Active Directory sites?

Run the Stop-DatabaseAvailabilityGroup cmdlet in the shell

To stop the database availability group, follow these steps:

  1. On a server in the recovery datacenter, use the Exchange Management Shell to run the following command:
    Stop-DatabaseAvailabilityGroup –Identity <DAG_Name>  -ActiveDirectorySite <Primary_Site>   - ConfigurationOnly:$True
  2. Repeat step 1 for all Active Directory sites that are not the recovery datacenter Active Directory site.

To verify that the command completed correctly, follow these steps:

  1. Verify that the servers are stopped by viewing the StartedMailboxServers and StoppedMailboxServers lists for the DAG. To do this, run the following command in the shell: Get-DatabaseAvailabilityGroup –Identity <DAG_Name>  | FL The StoppedMailboxServer list should show all mailbox servers in the primary datacenter and the StartedMailboxServers list should show all mailbox servers in the recovery datacenter.

Note: If a domain controller in the primary datacenter is not available, the Stop-DatabaseAvailabilityGroup command may return an Active Directory provider error. This error can be safely ignored.


Did the Stop-DatabaseAvailabilityGroup command complete correctly?

Run the Stop-DatabaseAvailabilityGroup cmdlet in the shell

To stop the database availability group, follow these steps:

  1. On a server in the recovery datacenter, use the Exchange Management Shell to run the following command:
    Stop-DatabaseAvailabilityGroup –Identity <DAG_Name>  -MailboxServer <DAG_Member_In_Primary>  - ConfigurationOnly:$True
  2. Repeat step 1 for all DAG members that are not in the recovery datacenter Active Directory site.

To verify that the command completed correctly, follow these steps:

  1. Verify that the servers are stopped by viewing the StartedMailboxServers and StoppedMailboxServers lists for the DAG. To do this, run the following command in the shell: Get-DatabaseAvailabilityGroup –Identity <DAG_Name>  | FL
    The StoppedMailboxServer list should show all mailbox servers in the primary datacenter and the StartedMailboxServers list should show all mailbox servers in the recovery datacenter.

Note: If a domain controller in the primary datacenter is not available, the Stop-DatabaseAvailabilityGroup command may return an Active Directory provider error. This error can be safely ignored.


Did the Stop-DatabaseAvailabilityGroup command complete correctly?

Physical access to a primary data center

Complete this step if you have physical access to a primary data center that is not connected by a network. If you cannot complete this step, go to the next step.

  1. If Exchange Management Shell access to the primary datacenter is available, run the following command:
    Stop-DatabaseAvailabilityGroup –Identity <DAG_Name>  -ActiveDirectorySite<Primary_Site>
  2. Repeat step 1 for all additional Active Directory sites that are not the recovery datacenter Active Directory site.

To verify that the command completed correctly, follow these steps:

  1. Verify that the servers are stopped by viewing the StartedMailboxServers and StoppedMailboxServers lists for the DAG. To do this, run the following command in the shell: Get-DatabaseAvailabilityGroup –Identity <DAG_Name>  | FL 
    The StoppedMailboxServer list should show all mailbox servers in the primary datacenter and the StartedMailboxServers list should show all mailbox servers in the recovery datacenter.
  2. Verify that the cluster services on all Exchange servers that were accessible in the primary datacenter were forcibly cleaned up. To do this, follow these steps on all Exchange servers that were accessible in the primary datacenter:
    1. Start Services.msc.
    2. In the Services list, locate Cluster Service.
    3. Verify that the parameter in the Startup Type list is set to Disabled.
    4. Close Services.
If the Startup Type is not set to Disabled, forcibly clean up the cluster services and then verify the Startup Type again. To forcibly clean up the cluster services, run the following command at a Command Prompt on all accessible Exchange Servers: Cluster node /forcecleanup.

Note: If a domain controller in the primary datacenter is not available, the Stop-DatabaseAvailabilityGroup command may return an Active Directory provider error. This error can be safely ignored.


Did the Stop-DatabaseAvailabilityGroup command complete correctly?

DAG extended to multiple Active Directory sites

Is your DAG extended to multiple Active Directory sites?

Run the Stop-DatabaseAvailabilityGroup cmdlet in the shell

To stop the database availability group, follow these steps:

  1. On a server in the recovery datacenter, use the Exchange Management Shell to run the following command:
    Stop-DatabaseAvailabilityGroup –Identity <DAG_Name>  -ActiveDirectorySite<Primary_Datacenter>  -ConfigurationOnly: $True
  2. Repeat step 1 for all Active Directory sites that are not the recovery datacenter Active Directory site.

To verify that the command completed correctly, follow these steps:

  1. Verify that the servers are stopped by viewing the StartedMailboxServers and StoppedMailboxServers lists for the DAG. To do this, run the following command in the shell: Get-DatabaseAvailabilityGroup –Identity <DAG_Name> | FL
    The StoppedMailboxServer list should show all mailbox servers in the primary datacenter and the StartedMailboxServers list should show all mailbox servers in the recovery datacenter.

Note: If a domain controller in the primary datacenter is not available, the Stop-DatabaseAvailabilityGroup command may return an Active Directory provider error. This error can be safely ignored.


Did the Stop-DatabaseAvailabilityGroup command complete correctly?

Run the Stop-DatabaseAvailabilityGroup cmdlet in the shell

To stop the database availability group, follow these steps:

  1. On a server in the recovery datacenter, use the Exchange Management Shell to run the following command:
    Stop-DatabaseAvailabilityGroup –Identity <DAG_Name >  -MailboxServer <DAG_Member_In_Primary_Site >  -ConfigurationOnly:$True
  2. Repeat step 1 for all DAG members that are not in the recovery datacenter.

To verify that the command completed correctly, follow these steps:

  1. Verify that the servers are stopped by viewing the StartedMailboxServers and StoppedMailboxServers lists for the DAG. To do this, run the following command in the shell: Get-DatabaseAvailabilityGroup –Identity <DAG_Name >  | FL
    The StoppedMailboxServer list should show all mailbox servers in the primary datacenter and the StartedMailboxServers list should show all mailbox servers in the recovery datacenter.

Note: If a domain controller in the primary datacenter is not available, the Stop-DatabaseAvailabilityGroup command may return an Active Directory provider error. This error can be safely ignored.


Did the Stop-DatabaseAvailabilityGroup command complete correctly?

You have physical access to a primary data center that is not connected by a network

Complete this step if you have physical access to a primary data center that is not connected by a network. If you cannot complete this step, go to the next step.

  1. If Exchange Management Shell access to the primary datacenter is available, run the following command:
    Stop-DatabaseAvailabilityGroup –Identity <DAG_Name>  -MailboxServer <DAG_Member_In_Primary_Site>
  2. Repeat step 1 for all DAG members that are not in the recovery datacenter.

To verify that the command completed correctly, follow these steps:

  1. Verify that the servers are stopped by viewing the StartedMailboxServers and StoppedMailboxServers lists for the DAG. To do this, run the following command in the shell: Get-DatabaseAvailabilityGroup –Identity <DAG_Name>  | FL
    The StoppedMailboxServer list should show all mailbox servers in the primary datacenter and the StartedMailboxServers list should show all mailbox servers in the recovery datacenter.

Note: If a domain controller in the primary datacenter is not available, the Stop-DatabaseAvailabilityGroup command may return an Active Directory provider error. This error can be safely ignored.


Did the Stop-DatabaseAvailabilityGroup command complete correctly?

DAG extended to multiple Active Directory sites

Is your DAG extended to multiple Active Directory sites?

Run the Stop-DatabaseAvailabilityGroup cmdlet in the shell

To stop the database availability group when you have Exchange Management Shell access to the primary datacenter, follow these steps:

  1. On a server in the recovery datacenter, use the Exchange Management Shell to run the following command:
    Stop-DatabaseAvailabilityGroup –Identity <DAG_Name>  -ActiveDirectorySite <Primary_Site>   -ConfigurationOnly:$True
  2. Repeat step 1 for all Active Directory sites that are not the recovery datacenter Active Directory site.

To verify that the command completed correctly, follow these steps:

  1. Verify that the servers are stopped by viewing the StartedMailboxServers and StoppedMailboxServers lists for the DAG. To do this, run the following command in the shell: Get-DatabaseAvailabilityGroup –Identity <DAG_Name>  | FL
    The StoppedMailboxServer list should show all mailbox servers in the primary datacenter and the StartedMailboxServers list should show all mailbox servers in the recovery datacenter.

Note: If a domain controller in the primary datacenter is not available, the Stop-DatabaseAvailabilityGroup command may return an Active Directory provider error. This error can be safely ignored.


Did the Stop-DatabaseAvailabilityGroup command complete correctly?

Run the Stop-DatabaseAvailabilityGroup cmdlet in the shell

To stop the database availability group, follow these steps:

  1. On a server in the recovery datacenter, use the Exchange Management Shell to run the following command:
    Stop-DatabaseAvailabilityGroup –Identity <DAG_Name>  -MailboxServer <DAG_Member_In_Primary_Site>- ConfigurationOnly:$True
  2. Repeat step 1 for all DAG members that are not in the recovery datacenter.

To verify that the command completed correctly, follow these steps:

  1. Verify that the servers are stopped by viewing the StartedMailboxServers and StoppedMailboxServers lists for the DAG. To do this, run the following command in the shell: Get-DatabaseAvailabilityGroup –Identity <DAG_Name>  | FL
    The StoppedMailboxServer list should show all mailbox servers in the primary datacenter and the StartedMailboxServers list should show all mailbox servers in the recovery datacenter.

Note: If a domain controller in the primary datacenter is not available, the Stop-DatabaseAvailabilityGroup command may return an Active Directory provider error. This error can be safely ignored.


Did the Stop-DatabaseAvailabilityGroup command complete correctly?

Restore-DatabaseAvailabilityGroup

Before you can start the Restore-DatabaseAvailabilityGroup procedure, the Stop- DatabaseAvailabilityGroup must be completed successfully. 


Did Stop-DatabaseAvailabilityGroup complete successfully?

Stop the Cluster service on each DAG member in the recovery datacenter

To stop the Cluster service on each DAG member in the recovery datacenter, follow these steps:

  1. At a command prompt, run one of the following commands, depending on the operating system being used by the DAG member:
    • For Windows Server 2008 R2, run the command Stop-Service Clussvc
    • For Windows Server 2008 SP2, run the command Net Stop Clussvc

Note: You must use an elevated command prompt (run as administrator) if the default administrator account is not used. If the command is not run as an administrator, you receive the error message "Access denied".

Cluster services are stopped on remaining nodes.


Is the Cluster service stopped on all DAG members in your recovery datacenter?

The Cluster service must be stopped(Placeholder)

Is the Cluster service stopped on all DAG members in your recovery datacenter?

Run the Restore-DatabaseAvailabilityGroup cmdlet in the shell

To restore the database availability group, follow these steps:

On a server in the recovery datacenter, use the Exchange Management Shell to run the following command:

Restore-DatabaseAvailabilityGroup –Identity <DAG_Name>  -ActiveDirectorySite <Recovery_Site>- AlternateWitnessDirectory:<AWSPath> - AlternateWitnessServer:<AWSName>


When you run this command, the following events occur:

  1. A DAG member in the recovery datacenter is randomly selected and its Cluster service is started in /forceQuourm mode
    • DAG members on the StoppedMailboxServers list are evicted from the DAG's cluster. This adjusts the membership count
    • If the resulting membership count is EVEN or results in a SINGLE node, the Cluster is configured by using a Node and File Share Majority quorum and it begins to use the Alternate Witness Server and Alternate Witness Directory
  2. Cluster services are started on the remaining DAG members and they successfully join the DAG's cluster

Verify that the DAG members are up and the Cluster Group is online.

To do this on a computer that is running Windows Server 2008 R2, run the following commands within powershell:

  • Import-Module FailoverClusters
  • Get-ClusterNode –Cluster <DAG_Name>
  • Get-ClusterGroup –Cluster <DAG_Name>

To do this on a computer that is running Windows Server 2008 SP2, run the following commands at a command prompt:

  • Cluster <DAG_Name>  node
  • Cluster <DAG_Name>  group

Note: If nodes are not evicted from the DAG's cluster and you receive error 0x46, see Exchange 2010: Restore- DatabaseAvailabilityGroup does not evict nodes error 0x46 for information about how to resolve this issue.


Did the Restore-DatabaseAvailabilityGroup command complete correctly?

Client access and database activation in the remote site

Start with procedures to address client access and database activation in the remote site.

This completes the datacenter switchover.


What do you want to do now?

Start Switchback

After a switchover is completed, you will want to reverse the server roles so that the original Master is the active server again and the Replica is the standby server again.

To start this procedure, bring the primary datacenter online .


Supporting Services

Make sure that following supporting services are running:

  • Active Directory / domain controllers / global catalog / FSMO role holders
  • Domain Name Services (DNS)
  • Witness Server
  • Supporting Exchange roles: Client Access and Hub Transport

The following optional services may also be needed:

  • Dynamic Host Configuration Protocol servers (DHCP), if DHCP addresses are used for DAG networks
  • Edge Transport server
  • Unified Messaging server

Note: Other services specific to your network may be needed.


Are all required services running as expected?

Supporting Services(Placeholder)

Make sure that following supporting services are running:

  • Active Directory / domain controllers / global catalog / FSMO role holders
  • Domain Name Services (DNS)
  • Witness Server
  • Supporting Exchange roles: Client Access and Hub Transport

The following optional services may also be needed:

  • Dynamic Host Configuration Protocol servers (DHCP), if DHCP addresses are used for DAG networks
  • Edge Transport server
  • Unified Messaging server

Note: Other services specific to your network may be needed.

Services(Placeholder)

Are all required services running as expected?

Verify network connectivity between all DAG members

To verify that all the DAG members are connected on the network, use one of the following methods:

  • Use the Ping command to test network connectivity between DAG members
  • Map administrative shares between DAG members to test network connectivity

After you verify that connectivity between datacenters is functioning and all cluster inter-node communications are operating correctly, go to the next step.


Have datacenter communications been verified to be working correctly?

Network connectivity verified(Placeholder)

Have datacenter communications been verified to be working correctly?

DAG members Cluster service startup type Disabled

Verify that Cluster service on the DAG members in the primary datacenter have startup type set to Disabled. If they do not, either the Stop-DatabaseAvailabilityGroup command was not successful or the DAG members in the primary datacenter did not receive eviction notification after network connectivity between datacenters was restored.

Follow these steps on all Exchange servers that were accessible in the primary datacenter:

  1. Start Services.msc.
  2. In the Services list, locate Cluster Service.
  3. Verify that the parameter in the Startup Type list is set to Disabled.
  4. Close Services.

If Cluster service cleanup has not occurred and Cluster service does not have the startup type set to Disabled, forcibly clean up the cluster services on the DAG members in the primary datacenter. To do this, run the following command at a Command Prompt on all DAG members: Cluster node /forcecleanup

Verify the Startup Type again.


Does the Cluster service show startup type as Disabled?

Cluster service disabled(Placeholder)

Does the Cluster service show startup type as Disabled?

DAG extended to multiple Active Directory sites

Is your DAG extended to multiple Active Directory sites?

Start-DatabaseAvailabilityGroup

Use the Exchange Management Shell to run the following command:

Start-DatabaseAvailabilityGroup –Identity <DAG_Name>  -ActiveDirectorySite <Primary_Site>

Repeat the command for all Active Directory sites that were stopped during the datacenter switchover process.

After you run this command, DAG members in the primary datacenter are added to the DAG's cluster.

If the resulting membership count is EVEN, the cluster will use the Node and File Share Majority quorum.

To verify that the DAG members are up and the Cluster Group is online , run the following commands:

  • In Windows Server 2008 R2, run the following commands within powershell:
    • Import-Module FailoverClusters
    • Get-ClusterNode –Cluster 
    •  Get-ClusterGroup –Cluster
  • In Windows Server 2008 SP2, run the following commands at a command prompt:
    • Cluster <DAG_Name>  node
    • Cluster <DAG_Name>  group

Run the following command: Get-DatabaseAvailabilityGroup –Identity <DAG_Name>  | FL

In the results, the StartedMailboxServers list should show all DAG members and the StoppedMailboxServers list should be empty.

Note: Nodes may not always join the cluster and you receive an invalid node error. If this occurs, retry the command.


Were the DAG members added to the cluster successfully?

Start-DatabaseAvailabilityGroup

Use the Exchange Management Shell to run the following command:

Start-DatabaseAvailabilityGroup –Identity <DAG_Name>  -MailboxServer  <DAG_Member_In_Primary_Site>

Repeat the command for all Mailbox servers that were stopped during the datacenter switchover process.

After you run this command, DAG members in the primary datacenter are added to the DAG's cluster.

If the resulting membership count is EVEN, the cluster will use the Node and File Share Majority quorum.

To verify that the DAG members are up and the Cluster Group is online , run the following commands in the shell:

  • In Windows Server 2008 R2, run the following commands:
    • Import-Module FailoverClusters
    • Get-ClusterNode –Cluster <DAG_Name>
    •  Get-ClusterGroup –Cluster <DAG_Name>
  • In Windows Server 2008 SP2, run the following commands:
    • Cluster <DAG_Name>  node
    • Cluster <DAG_Name>  group

Run the following command: Get-DatabaseAvailabilityGroup –Identity <DAG_Name>  | FL

In the results, the StartedMailboxServers list should show all DAG members and the StoppedMailboxServers list should be empty.

Note: Nodes may not always join the cluster and you receive an invalid node error. If this occurs, retry the command.


Were the DAG members added to the cluster successfully?

DAG members added to the cluster(Placeholder)

Were the DAG members added to the cluster successfully?

DAG members added to the cluster(Placeholder)

Were the DAG members added to the cluster successfully?

Reset the DAG's Witness Server and Alternate Witness Server properties

Reset the DAG's Witness Server and Alternate Witness Server properties

To reset the DAG's Witness Server and Alternate Witness Server properties, run the following command in the shell:

Set-DatabaseAvailabilityGroup –Identity <DAG_Name>-WitnessServer <Witness_Server_Name>-AlternateWitnessServer <Alternate_Witness_Server_Name>


When you run this command, the Witness Server and the Alternate Witness Server properties are configured so that the correct witness server is being used.

If the Cluster configuration does not match the DAG configuration, the Cluster is updated with the correct configuration.

Note: An error may occur if the incorrect file share witness is verified to be in use. For more information, see Exchange 2010 – File Share Witness oddities.


Remove Activation Blocks

After any activation blocks are removed , active database copies can be moved to servers in the primary datacenter


Did this solve your problem?

Remove Activation Blocks(Placeholder)

After any activation blocks are removed , active database copies can be moved to servers in the primary datacenter.


Did this solve your problem?

Contact Microsoft Support

If you encounter issues when you try to complete this procedure, click here to contact Microsoft Support for help. Once you open the support page, select the version of Exchange 2010 you are using.

On the Create an incident webpage, click Clustering and High Availability (Including Deployment) in the Problem type list, click Database Availability Group (DAG) in the Category list, and then click Start request in the Contact Microsoft area.

Congratulations, Exchange Server 2010 Datacenter Switchover is now completed.
Properties

Article ID: 10086 - Last Review: Feb 23, 2016 - Revision: 96

Feedback