Exchange2016 故障分析与处理
案例背景： 搭建Exchange 2016 DAG之后，其中有一台服务器出现故障，需要重新安装操作系统。
服务器环境：
| 操作系统 | 服务器名称 | 状态 |
| Server 2016 Std | SVRRZEX1 | 故障 |
| Server 2016 Std | SVRRZEX2 | 正常 |
处理步骤：
1. 将故障服务器从DAG中删除：
使用 Remove-DatabaseAvailabilityGroupServer cmdlet 从 DAG 中删除故障服务器的配置：
Remove-DatabaseAvailabilityGroupServer -Identity DAG -MailboxServer SVRRZEX1 -ConfigurationOnly
2. 重新安装系统并配置SVRRZEX1
Install-WindowsFeature RSAT-ADDS
Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, RSAT-Clustering-PowerShell, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation
Setup /m:RecoverServer /IAcceptExchangeServerLicenseTerms
3.检查状态
Get-exchangeserver
Get-mailboxdatabase
Add-DatabaseAvailabilityGroupServer -Identity DAG -MailboxServer SVRRZEX1
这时出现问题，提示无法加入，经过分析后得知，问题是由于第一步中使用的ConfigurationOnly这个参数非正常退出的DAG组，因此需要先手动将SVRRZEX1这个Node从Cluster中删除
4.删除故障转移群节点
cluster node <computername> /forcecleanup
so in the case of my alpineskihouse.com laptop-server, I would open a command prompt (Run As Administrator) and type:
cluster node SVRRZEX1 /forcecleanup
5.尝试重新加入DAG，依然出现错误，需要重新建立DAG，将SVRRZEX2节点也删除
cluster node SVRRZEX2 /forcecleanup
然后将Cluster删除
cluster DAG /DESTROY
6.重新创建DAG，然后重新加入，成功
Add-DatabaseAvailabilityGroupServer -Identity DAG -MailboxServer SVRRZEX1
Add-DatabaseAvailabilityGroupServer -Identity DAG -MailboxServer SVRRZEX2
7.检查故障转移群，重新创建DAG数据库备份等后续工作。。。。
参考文章URL：
https://blogs.technet.microsoft.com/canitpro/2012/02/14/how-to-clean-up-cluster-nodes-from-destroyed-clusters/
http://www.mamicode.com/info-detail-1144040.html
