- MAPI traffic = users accessing their mailbox via Outlook.
- Replication traffic = log files of a primary (active) copy of a given database being copied to the server(s) holding the passive copy of the database. In our case, there is a single passive copy. There could be up to 16 copies.
We configure the MAPI NIC as follows:
One word on IPv6.
File Share Witness (FSW)
Create the DAG
We can use the EMC or the EMS to create the DAG. I will use the latter.
There are three major steps in the creation of a DAG:
- The creation of the DAG itself
- Adding mailbox servers to the DAG
- Selecting mailbox databases that will be part of the DAG
So I'll start by creating the DAG itself.
I thought that all was ready but when I execute the following command...
[PS] C:\>New-DatabaseAvailabilityGroup -Name DAG1 -WitnessServer FSW1.mynet.lan -WitnessDirectory C:\FSW -DatabaseAvailabilityGroupIpAddresses 10.0.0.25
I already encounter an error:
First, I know:
- I have added the Exchange Trusted Subsystem to the local administrators group
- I have added the File Server role.
[PS] C:\>Set-DatabaseAvailabilityGroup DAG1 -WitnessServer FSW1.mynet.lan -WitnessDirectory C:\FSW_DAG1
PS C:\> Enable-PSRemoting
This is more or less the equivalent of the command winrm quickconfig and accomplishes the following:
1. Starting or restarting (if already started) the WinRM service
2. Setting the WinRM service type to auto start
3. Creating a listener to accept requests on any IP address
4. Enabling firewall exception for WS-Management traffic (for http only).
In any case, this allowed me to add servers to the DAG with these cmdlets:
PS] C:\>Add-DatabaseAvailabilityGroupServer DAG1 -MailboxServer EX13-1
[PS] C:\>Add-DatabaseAvailabilityGroupServer DAG1 -MailboxServer EX13-2
Finally, I can designate a mailbox database to be part of the DAG. This translates into the creation of a second copy of the database on the second server. Mailbox database "DB1" already exists on server EX13-1 where I created it. With the following cmdlet, a second copy will be created on server EX13-2:
[PS] C:\>Add-MailboxDatabaseCopy DB1 -MailboxServer EX13-2 -ActivationPreference 2
This concludes my first blog post on Database Availability Groups.