{"id":235,"date":"2011-03-30T20:59:54","date_gmt":"2011-03-30T20:59:54","guid":{"rendered":"http:\/\/tech-no.104.210.61.21.xip.io\/?p=235"},"modified":"2011-05-16T16:57:43","modified_gmt":"2011-05-16T16:57:43","slug":"windows-2008-r2-dfs-replication-troubleshooting-with-event-id","status":"publish","type":"post","link":"https:\/\/tech-no.org\/?p=235","title":{"rendered":"Windows 2008 R2 DFS replication troubleshooting with event ID:"},"content":{"rendered":"

\"\"<\/a><\/p>\n

Earlier this week i was tasked with troubleshooting the DFS replication for a development environment at work. I figured the issue was related to staging quota settings, so i ran a DFS Replication Health Report.<\/p>\n

After reviewing the report i found the following error:<\/p>\n

A USN journal wrap occurred 1 times in the past 7 days on E:. DFS Replication monitors the USN journal to detect changes made to the replicated folder. A USN journal wrap occurs when large numbers of files change so quickly that the USN journal must discard the oldest changes (before DFS Replication has had a chance to detect the changes) to stay within the specified size limit of the USN journal. Although DFS Replication automatically recovers from this problem, replication stops temporarily for replicated folders stored on this volume. Repeated journal wraps usually indicate that the USN journal is too small. Event ID: 2202<\/p><\/blockquote>\n

After a quick search i was able to find the tool to change the USN journal size and report on current settings. FSUTIL seems to be used for quite a bit more than hardlinks etc.<\/p>\n

I found an article that touched on what what happening but unfortunately didnt work as it was for windows 2000 server.<\/p>\n

http:\/\/social.technet.microsoft.com\/Forums\/en-US\/winservergen\/thread\/d3028088-d5fb-4a28-8ba2-7f9628a5f3bc<\/a><\/p>\n

http:\/\/support.microsoft.com\/kb\/292438<\/a><\/p>\n

 <\/p>\n

Here is how you determine the Max size of the USN journal (be sure to replace your drive letter at the end of the command)<\/p>\n

fsutil usn queryjournal e:<\/p><\/blockquote>\n

my results from this command looked like this:<\/p>\n

C:\\Windows\\system32>fsutil usn queryjournal e:
\nUsn Journal ID\u00a0\u00a0 : 0x01cbceef195bdf41
\nFirst Usn\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 : 0x0000000275c00000
\nNext Usn\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 : 0x0000000295e3d420
\nLowest Valid Usn : 0x0000000000000000
\nMax Usn\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 : 0x7fffffffffff0000
\nMaximum Size\u00a0\u00a0\u00a0\u00a0 : 0x0000000020000000
\nAllocation Delta : 0x0000000000400000<\/p><\/blockquote>\n

I decided to adjust the value to 2gb and see what happens. The following steps are needed to complete this change:<\/p>\n

run the following command from the server with the drive you wish to change the USN journal size<\/p>\n

 <\/p>\n

fsutil usn createjournal m=2147483648 a=1 e:<\/p><\/blockquote>\n

Notice the drive letter is at the end of the command, so enter your drive letter here.<\/p>\n

I used the microsoft calculator in programmer mode to convert HEX to decimal and then used an online bit calculator to convert the output to use in the command<\/p>\n

http:\/\/www.matisse.net\/bitcalc\/<\/a><\/p>\n

 <\/p>\n

If you run the command again to query the journal your output would look like this:<\/p>\n

C:\\Windows\\system32>fsutil usn queryjournal e:
\nUsn Journal ID\u00a0\u00a0 : 0x01cbceef195bdf41
\nFirst Usn\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 : 0x0000000278800000
\nNext Usn\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 : 0x0000000298a8dab0
\nLowest Valid Usn : 0x0000000000000000
\nMax Usn\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 : 0x7fffffffffff0000
\nMaximum Size\u00a0\u00a0\u00a0\u00a0 : 0x0000000080000000
\nAllocation Delta : 0x0000000000400000<\/p>\n

 <\/p>\n

I will post later about the results from this change. according to what i read online it will either fix the issue or require a larger USN journal. If anyone knows the max setting i would love to know them<\/p>\n

Hopefully this information helps someone looking for the solution to DFS replication issues on windows 2008 R2.<\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

Earlier this week i was tasked with troubleshooting the DFS replication for a development environment at work. I figured the issue was related to staging quota settings, so i ran a DFS Replication Health Report. After reviewing the report i found the following error: A USN journal wrap occurred 1 times in the past 7 …<\/p>\n","protected":false},"author":7,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[5],"tags":[],"_links":{"self":[{"href":"https:\/\/tech-no.org\/index.php?rest_route=\/wp\/v2\/posts\/235"}],"collection":[{"href":"https:\/\/tech-no.org\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/tech-no.org\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/tech-no.org\/index.php?rest_route=\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"https:\/\/tech-no.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=235"}],"version-history":[{"count":3,"href":"https:\/\/tech-no.org\/index.php?rest_route=\/wp\/v2\/posts\/235\/revisions"}],"predecessor-version":[{"id":238,"href":"https:\/\/tech-no.org\/index.php?rest_route=\/wp\/v2\/posts\/235\/revisions\/238"}],"wp:attachment":[{"href":"https:\/\/tech-no.org\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=235"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/tech-no.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=235"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/tech-no.org\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=235"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}