DFS not replicating

Hello everyone,
I am having a strange issue.  I have created a test document to verify DFS replication between two servers and to my shock it did not replicate and I also see that the files are not matching up.  I have tried the following:

I looked in Event Viewer and could not find any recent errors
I successfully verify the topology
I created a diagnostic report and no errors were found

It seems that all of the tools that I have at my disposal are saying that everything is working fine, but the files are not replicating.  Please let me know if you guys have any suggestions or if more information is needed.

Thank you!!!
LVL 1
Kurt SutulaAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

8046586Commented:
Run the AD replication status tool:
https://blogs.technet.microsoft.com/askds/2012/08/23/ad-replication-status-tool-is-live/
I hope this might help
0
8046586Commented:
Check this article too. It is related to Server 2012 but might be something similar to your issue (read the knowing issue in this update). Try running the latest rollup for 2008 server.

https://support.microsoft.com/en-us/help/3156418/may-2016-update-rollup-for-windows-rt-8-1--windows-8-1--and-windows-se
0
Jason CrawfordTransport NinjaCommented:
Run this wmic command to check the state:

wmic /namespace:\\root\microsoftdfs path DfsrReplicatedFolderInfo get replicatedFolderName, State

Did you pre-stage the data on the downstream server during the initial sync?
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Shaun VermaakTechnical SpecialistCommented:
How many DCs? If this DC holds no FSMOs you can quickly rebuild it from IFM which contains SYSVOL

You using DFSR or FRS?
0
Kurt SutulaAuthor Commented:
I just tried the replication status tool, switched it to errors only and I got no errors.  These are the results that I get when I run the command that Jason told me to run:
ReplicatedFolderName  State
SYSVOL Share          4
ets                   4
Home                  4
Public                4

I am using DFSR. There are two Domain controllers for this environment.  They are linked via site to site VPN.  I don't believe that it was pre staged.  This was setup and working before I started working for this company.
0
Jason CrawfordTransport NinjaCommented:
4 indicates the initial sync was completed successfully.  You need to check replication backlog now:

dfsrdiag backlog /rgname:<Replication Group Name> /rfname:<Folder Name> /sendingmember:<Upstream Server> /receivingmember:<Downstream Server>

Open in new window

You can optionally try forcing a sync:

dfsrdiag syncnow /partner:<DFS Partner Server Name> /RGName:<Replication Group> /Time:1

DFSRDIAG POLLAD /MEM:%computername%

Open in new window

0
Jason CrawfordTransport NinjaCommented:
Keep in mind also that some file extensions may be excluded from syncing.  Also temp files (e.g. downloaded from the internet) may also cause sync issues.
0
Kurt SutulaAuthor Commented:
Ok so the first one just checks the status and the second one forces the sync right?  I want to do manual backup of that data before I force a sync.
0
Jason CrawfordTransport NinjaCommented:
Yes sir that is correct and good thinking :)  Just make sure that backup is application aware.  Just as with Active Directory or Exchange DBs in a DAG, DFS is a multi-master database so if you try to restore a non-application aware backup you're gonna have a bad time.
0
Kurt SutulaAuthor Commented:
Just as an update guys, the test document that I have created before went through.  Prior I did do a replication via sites and services.  I am not sure if that has anything to do with it or if it is just taking really long to replicate.
0
Kurt SutulaAuthor Commented:
Hey guys,
I just checked the replication schedule and it turns out that I did test it  outside of that.  I will wait until the next cycle and check it.  If that was the problem, then I am sorry that I wasted everyone's time.
0
Jason CrawfordTransport NinjaCommented:
Not a waste at all...glad you got it figured out.  If you found any of our solutions helpful please  mark them as the solution.
0
Kurt SutulaAuthor Commented:
Well,
I'll check it after 6:00pm today and let you guys know.  If the other test document goes through and it turns out that was the issue all along, do you guys want me to delete this or mark that my answer as best answer?
0
Kurt SutulaAuthor Commented:
It was because of the sync schedule.  The test document went through.  Sorry guys it was a layer 8 issue lol
1

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
8046586Commented:
good, at least you have it running
0
Kurt SutulaAuthor Commented:
This was the reason for the issue
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Distributed File System (DFS)

From novice to tech pro — start learning today.