dfs replication event

dfs replication event

If you have experienced a dirty shutdown on one of your Domain controller, you may notice that this is now not able to receive replicated data from the other domain controllers or we can also say its replication partners.you can find the details error information while running the DCDIAG, it show you about DFS-R test failed .Kindly go through event viewer and search event ID 2213 in the DFS Replication event logs.

DFS Replication service stopped

DFSR event ID 2213 in Windows Server 2008 R2 or Windows Server 2012Event ID 2213 is logged on your DFSR server.

The DFS Replication service stopped replication on volume X:. This occurs when a DFSR JET database is not shut down cleanly and Auto Recovery is disabled. To resolve this issue, back up the files in the affected replicated folders, and then use the ResumeReplication WMI method to resume replication.

Additional Information:

Volume: X:

GUID: AB136C85-E682-11E8-93FB-009C02A3DAB4

Recovery Steps

• Back up the files in all replicated folders on the volume. Failure to do so may result in data loss due to unexpected conflict resolution during the recovery of the replicated folders.
• To resume the replication for this volume, use the WMI method ResumeReplication of the DfsrVolumeConfig class. For example, from an elevated command prompt, type the following command:

wmic /namespace:\\root\microsoftdfs path dfsrVolumeConfig where volumeGuid="AB136C85-E682-11E8-93FB-009C02A3DAB4" call ResumeReplication

Recovery Steps

• Backup all your data folders for the affected replicated folder
• Open the event ID 2213 and you will see in Step 2 that if gives you the command you need to run from an evelated command prompt. For example: wmic /namespace:\\root\microsoftdfs pathdfsrVolumeConfig where volumeGuid=”F1CF316E-6A40-11E2-A826-00155D41C919″ call ResumeReplication.

• Remember the volumeGuid is specific to that volume, so make sure it is the correct volume from event id 2213.When completed you should see this output in the command prompt:

• Check whether event IDs 2212 and 2214 have been logged on the server on which you ran the resume replication command:

Event Type: Warning
Event Source: DFSR
Event Category: Disk
Event ID: 2212
Description:
“The DFS Replication service has detected an unexpected shutdown on volume X:. This can occur if the service terminated abnormally (due to a power loss, for example) or an error occurred on the volume. The service has automatically initiated a recovery process. The service will rebuild the database if it determines it cannot reliably recover. No user action is required.

Event Type: Warning
Event Source: DFSR
Event Category: Disk
Event ID: 2214
Description:
“The DFS Replication service successfully recovered from an unexpected shutdown on volume E:.This can occur if the service terminated abnormally (due to a power loss, for example) or an error occurred on the volume. No user action is required".

• Post this command Kindly do the health check of domain controller. Now your domain controller start receiving the replication changes from its partner domain controller.

For more information around DFSR no longer replication file, Invocation Id and USN rollback , review:

• DFSR no longer replicates files
• Invocation ID in Active Directory
• USN in Active Directory

So, that’s all in this blog. I will meet you soon with some other stuff. Have a nice day !!!

Recommended content

RODC Installation Guide- Step by step guide to install read only domain controller

RODC Filtered Attribute Set

Installing and configuring a RODC in Windows Server-2012

How to find the GUID of Domain Controller

Understanding Group Policy Preferences

Group Policy Verification Tool GPOTool Exe

Group Policy Health Check on Specific Domain Controller

Netlogon Folder in Active Directory

Custom Attributes in Active Directory

Tombstone Lifetime of My Active Directory Forest

Computers AD Site From the Command Line

Active Directory Database Integrity

Disabling and Enabling the Outbound Replication

DFS Replication Service Stopped Replication

Strict Replication Consistency

The replication operation failed because of a schema mismatch between the servers involved

Troubleshooting ad replication error 8418 the replication operation failed because of a schema mismatch between the servers

Replication information in txt file

Repadmin Replsummary

Enabling the outbound replication

Guys please don’t forget to like and share the post.Also join our WindowsTechno Community and where you can post your queries/doubts and our experts will address them .

You can also share the feedback on below windows techno email id.

If you have any questions feel free to contact us on admin@windowstechno.com also follow us on facebook@windowstechno to get updates about new blog posts.