Windows 2012 DC 同步异常处理

今天早上，创建了一个新的组策略，结果发现一个远程办公室的客户端始终没有更新，运行gpupdate 直接就报错。通过仔细检查，发现当地域控的sysvol里面根本就没有同步新建立的policy。在AD sites and service里面进行replicate也毫无效果。


最后在event viewer里面逐条查看记录，发现了大量的 DFSR unexpected shutdown recovery的警告日志，最先的时间是从10号开始的，换句话说，3个礼拜前，这个域控就不一样步了~

The DFS Replication service stoppedreplication on volume E:. This occurs when a DFSR JET database is not shut downcleanly and Auto Recovery is disabled. To resolve this issue, back up the filesin the affected replicated folders, and then use the ResumeReplication WMImethod to resume replication.

Additional Information:
Volume: E:
GUID: C2B76452-2993-11E3-93F5-00155D801816

Recovery Steps
1. Back up the files in all replicatedfolders on the volume. Failure to do so may result in data loss due tounexpected conflict resolution during the recovery of the replicated folders.
2. To resume the replication for thisvolume, use the WMI method ResumeReplication of the DfsrVolumeConfig class. Forexample, from an elevated command prompt, type the following command:
wmic /namespace:\\root\microsoftdfs pathdfsrVolumeConfig wherevolumeGuid="C2B76452-2993-11E3-93F5-00155D801816" callResumeReplication

For more information, see http://support.microsoft.com/kb/2663685.




通过搜索，我在这个博客里面找到了答案
http://blogs.technet.com/b/filecab/archive/2013/07/31/dfs-replication-in-windows-server-2012-r2-revenge-of-the-sync.aspx

缘由很简单，在2012以前的时代，若是同步异常，好比DC重启之类的，那么他会自动从新进行同步；可是这种方式会默认本地的信息无效，而自动从远程的DC拷贝“最新信息“覆盖，这样可能会形成一些信息的丢失；在最新的2012中，若是出现了同步异常，他须要管理员手动同步，这样能够先进行备份避免丢失本地信息。事实上，从上面的event viewer里面会直接提示如何操做。 并且这个操做也确实是有效的。执行以后，新的日志代表

TheDFS Replication service successfully recovered from an unexpected shutdown onvolume E:.This can occur if the service terminated abnormally (due to a powerloss, for example) or an error occurred on the volume. No user action isrequired.


几分钟以后，个人组策略也成功同步工做了


头一次遇见这个问题，2012 不少东西都不同了~