EXCHANGE 2013 - CONFIGURING DATABASE AVAILABIL/div>
A database availability group (DAG) is a collection of servers that provides the infrastructure for replicating and activating database copies. The DAG uses continuous replication to each of the passive database
copies within the DAG.
In this article I will show how to configure DAG and fault tolerance testing by DAG.
In my LAB, I use five computers:
- DC2012: Domain Controller (domain mcthub.local) running Windows Server 2012
- EXCHANGE1 and EXCHANGE2: Domain Member running Windows Server 2012 and Exchange Server 2013 (Mailbox Role and Client Access
Role)
- FILESERVER: Domain Member running Windows Server 2012 (File Share Witness Server). I recommend that you configure the witness
server on a Client Access server in the Exchange Server organization. The additional load on the server is minimal, and it is already under the control of the Exchange Server management group. The witness server does not need to run the same version of Windows
Server as the members of the DAG. The file share witness also requires the File Server feature installed
- CLIENT1: Domain Member running Windows 8 and Outlook 2013
Because the file share witness server is not an Exchange server, some additional permissions are required. The Exchange Trusted Subsystem group in Active Directory must be added to
the local Administrators group on the file share server.
And you should verify that File and Printer Sharing is allowed through the firewall. Open Windows Firewall (FIREWALL.CPL) - Select "Allow an app or feature through Windows
Firewall"
- Verify File and Printers Sharing is selected- OK
Pre-stage the cluster network object for a DAG
- On DC2012, in Server Manager, click Tools, and then click Active Directory Users and Computers. On
the menu bes New Roman';font-size:medium;">
Pre-stage the cluster network object for a DAG View, and then click Advanced Features.
- Create a Computers Account
- Type an arbitrary name (DAG1) - OK
- On Security tab, grant the computer account for the first DAG member (EXCHANGE1) and the Exchange Trusted Subsystem group Full Control
- Click OK
- Then disable the computer account.
Create a DAG and add mailbox servers to the DAG
- Switch to EXCHANGE1. Open Internet
Explorer, and type https://exchange1.mcthub.local/ecp, and
then press Enter. Navigate to servers - databases, You observe the system, I have two
mailbox servers included EXCHANGE1 and EXCHANGE2. EXCHANGE1 hosting
Mailbox Database named Mailbox Database 1
- Now I will create a DAG. Navigate to servers - database availability groups, Click the New (+) icon
-Enter the following details for the new DAG and Click Save when you have entered all of the required details
DAG name – this should match the comnputer account name you pre-staged earlier
Witness server – this is required for all DAGs
Witness directory – this is optional. If you do not specify a directory Exchange will choose one for you.
IP address – the DAG requires an IP address on each IP subnet that is part of the MAPI network. If you do not specify IP addresses the
DAG will use DHCP instead.
- After the DAG has been created it still does not contain any members. These need to be added next.
click the icon to manage DAG membership
- Click Add (+) icon
- After the DAG has been created it still does not contain any members. These need to be added next.
click the icon to manage DAG membership
- Click Add (+) icon
- Select both servers, then click Add button
- Click OK button
- Verify membership of the DAG and click Save button
- Note that this might take some time, so please wait.
- Click Close button when finished.
- Done, DAG has been created successfully
Create a mailbox database copy
- Navigate to servers - databases. Refresh the view- Click Mailbox Database 1, Click More (…) - click Add
database copy.
- Click Browse button
- Select server EXCHANGE2 - Click OK button
- Click Save button
- Wait until the saving completes successfully
- Click Save button
- Wait until the saving completes successfully
- Then click close when finished
- Verify successful completion of copying a database. In databases tabs, click Refresh, and wait until the details pane shows Mailbox Database 1\EXCHANGE2
as Passive Healthy. This might take several minutes and up to several hours depending on the size of the database. Make sure that the Status displays
Healthy and the Content index state also displays Healthy. Then click cancel. Note that this might take some time, so please wait.
- Or you can also use Get-MailboxDatabaseCopyStatus to
check the database copy health
- You can also use the below command to check the synchronization process
Verify successful completion of passive database
- To move Mailbox Database 1 to EXCHANGE2 I can simply highlight it and then review the status of the database copies. Note that in this case the passive copy on EXCHANGE2 is healthy, with no copy queue length
issues and a healthy content index state as well.
Under those conditions we can proceed with the switchover by clicking the link to Activate the database copy
- Click Yes to confirm the action
- Then a progress bar let’s you know when the operation is complete, so please wait
- Click Close when finished
- I can see that Mailbox Database 1 is now active on server EXCHANGE2..
- Or you can also use Get-MailboxDatabaseCopyStatus to
check the result
- Switch to CLIENT1, logon any user, open Outlook and check the user can still access the mailbox
Check the fault tolerance of the DAG
- Switch to EXCHANGE2, disable Network Adapter
- Switch to EXCHANGE1, I can see that Mailbox Database 1 is now active on server EXCHANGE1
- Switch to EXCHANGE1, I can see that Mailbox Database 1 is now active on server EXCHANGE1
- Switch to CLIENT1, logon any user, open Outlook and check the user can still access the mailbox
Thank you for reading my article To view my article in Vietnamese, click the link below
Configuring Permissions on the File Share Witness
- Configuring Permissions on the File Share Witness
- Or you can also use Get-MailboxDatabaseCopyStatus
mcthub.com
Resources For IT Professionals