Applies to: Exchange Server 2013
Topic Last Modified: 2012-11-02
If a Mailbox server that's a member of a database availability group (DAG) is lost or otherwise fails and is unrecoverable and needs replacement, you can perform a server recovery operation. Microsoft Exchange Server 2013 Setup includes the switch /m:RecoverServer that can be used to perform the server recovery operation. Running Setup with the /m:RecoverServer switch causes Setup to read the server's configuration information from Active Directory for a server with the same name as the server from which you're running Setup. After the server's configuration information is gathered from Active Directory, the original Exchange files and services are then installed on the server, and the roles and settings that were stored in Active Directory are then applied to the server.
Looking for other management tasks related to DAGs? Check out Managing Database Availability Groups.
What do you need to know before you begin?
- Estimated time to complete: 30 minutes
- You need to be assigned permissions before you can perform this
procedure or procedures. To see what permissions you need, see the
"Mailbox database copies" entry in the High Availability and
Site Resilience Permissions topic.
- If Exchange is installed in a location other than the default
location, you must use the /TargetDir Setup switch to
specify the location of the Exchange program files. If you don't
use the /TargetDir switch, the Exchange program files will
be installed in the default location
To determine the install location, follow these steps:
- Open ADSIEDIT.MSC or LDP.EXE.
- Navigate to the following location:
Group,CN=Administrative Groups,CN=ExOrg Name,CN=Microsoft
- Right-click the Exchange server object, and then click
- Locate the msExchInstallPath attribute. This attribute
stores the current installation path.
- Open ADSIEDIT.MSC or LDP.EXE.
- For information about keyboard shortcuts that may apply to the
procedures in this topic, see Keyboard Shortcuts in
the Exchange Admin Center.
Use Setup /m:RecoverServer to recover a server
- Retrieve any replay lag or truncation lag settings for any
mailbox database copies that exist on the server being recovered by
using the Get-MailboxDatabase
Get-MailboxDatabase DB1 | Format-List *lag*
- Remove any mailbox database copies that exist on the server
being recovered by using the Remove-MailboxDatabaseCopy
- Remove the failed server's configuration from the DAG by using
Remove-DatabaseAvailabilityGroupServer -Identity DAG1 -MailboxServer MBX1
Note: If the DAG member being removed is offline and can't be brought online, you must add the ConfigurationOnly parameter to the preceding command.
- Reset the server's computer account in Active Directory. For
detailed steps, see Reset a Computer Account.
- Open a Command Prompt window. Using the original Setup media,
run the following command.
- When the Setup recovery process is complete, add the recovered
server to the DAG by using the Add-DatabaseAvailabilityGroupServer
Add-DatabaseAvailabilityGroupServer -Identity DAG1 -MailboxServer MBX1
- After the server has been added back to the DAG, you can
reconfigure mailbox database copies by using the Add-MailboxDatabaseCopy
cmdlet. If any of the database copies being added previously had
replay lag or truncation lag times greater than 0, you can use the
ReplayLagTime and TruncationLagTime parameters of the
cmdlet to reconfigure those settings.
Add-MailboxDatabaseCopy -Identity DB1 -MailboxServer MBX1 Add-MailboxDatabaseCopy -Identity DB2 -MailboxServer MBX1 -ReplayLagTime 3.00:00:00 Add-MailboxDatabaseCopy -Identity DB3 -MailboxServer MBX1 -ReplayLagTime 3.00:00:00 -TruncationLagTime 3.00:00:00
How do you know this worked?
To verify that you've successfully recovered the DAG member, do the following:
- In the Shell, run the following command to verify the health
and status of the recovered DAG member.
Get-MailboxDatabaseCopyStatus -Server <ServerName>