We help IT Professionals succeed at work.

Two shares in full mesh are only replicating one way.

Medium Priority
990 Views
Last Modified: 2012-05-06
Hello,

I have been trying to resolve this issue for quite some time now.  I have two shares, each on a different server in the same domain, in a full mesh topology.  However, the shares are only syncing one way.

I stopped replication and then re-enabled it.  When I re-enabled it, I set Server A to be the master so all the files would get pushed from it to Server B.  Now, Server B syncs with Server A's changes, but Server A doesn't sync with Server B's changes.

In DFS, both DFS Referrals are enabled and file replication is enabled for both shares.  Both shares are shown as having an online status.  Active Directory Replication Monitor shows everything as being fine.  Meaning, that it states, for both servers, that replications were successful.  There are no 13508 errors, or any FRS/DFS errors, in the event log.  repadmin /showreps shows everything as being successful.  Windows firewall is off and there is nothing between the two servers that could be blocking traffic.  The FRS-Staging folders are showing transactions.  The schedule is setup to sync at all times.  The FRS, DFS and WMI services are running on both servers.

The only anomaly I can find is a folder on Server A called 'De8'.  This folder fluctuates in size with the actual contents of the share.  So, inside the share, there is this folder which is filling up with the shares contents, almost like a backup.  I deleted this folder before (previously called 'De7') and it came back as De8.  I'm not sure what this folder is or what it does.  The other thing I found was when using WinMerge to track the differences in the two shares, it showed a bunch of folders called 'DO_NOT_REMOVE_NtFrs_PreInstall_Directory' which I don't even see in Server A's share.  Only WinMerge shows them.  Show hidden files and folders is checked for this share.  I'm not sure what these folders are either.

Regardless, I would like some help to determine why files are only replicating one way in my full mesh DFS/FRS setup.  Server A syncs to Server B but Server B doesn't sync to Server A.  I hope I have provided you with enough information.

Thanks in advance,

Morgan
Comment
Watch Question

Are they all getting the replication as a final product? It could be that all the other mesh connections are redundant, and will only be used if the primary connection fails.
Try shutting one of the primary connections down and see if the redundant are used as a secondary.

Author

Commented:
I unchecked the connection from Server A to Server B and left the connection checked from Server B to Server A.  I then added a folder on Server B, forced a sync via replmon, and still the folder did not show up on Server A.

Commented:
You may want to turn on hidden file/folder view if you can't see 'DO_NOT_REMOVE_NtFrs_PreInstall_Directory' from widows explorer.
This is created as a backup during your replication configuration. For example, if you have data in Server A as well as data in server B, when you create dfs replication to start, like replicate from Server A to Sever B, the folder will first move all the data in server B into 'DO_NOT_REMOVE_NtFrs_PreInstall_Directory' so that you don't lose everything there by the replication.


Commented:
Are the two shares on member servers or domain controllers? and how do you access the share or are you looking locally at the servers?

Author

Commented:
View hidden files/folders is turned on for both shares.  I am accessing the shares locally on each server.  They are both DC's running Active Directory.  I know when we make changes in ADUC on Server A they get pushed down to Server B and changes made on Server B's ADUC do not get pushed to Server A.

Commented:
am I hearing this correctly, your AD is not doing replication?
I'm testing that now to make sure.  But, I'm pretty positive that it only replicates from Server A to Server B.  I'll get back to you on that.

So, in a turn of luck, it looks like the shares are syncing correctly.  You know the 'De8' folder I mentioned earlier?  The folder that said was created out of nowhere (probably by DFS) and was fluctuating in size?  Well, it turns out it wasn't fluctuating.  Yesterday it contained around 1,500 files and was rising.  The last time I checked it yesterday it was around 2,500.  This morning when I checked it, it was around 400 files.  When I tested syncing between the shares one last time before I sent this update, IT WORKED.  I used WinMerge to check the differences between the shares, and no more 'DO_NOT_REMOVE_NtFrs_PreInstall_Directory'.  I then decided to check the 'De8' folder and it was empty.  I guess once DFS has finished doing it's thing (technical term), it allows syncing both ways to occur.  It still doesn't make much sense to me.  Why it would only allow for syncing one way while that folder emptied itself.  If you have any insight, please share.

While I was typing, AD synced both ways.

Not the solution you were looking for? Getting a personalized solution is easy.

Ask the Experts

Commented:
It seems your DFS Replication is working. As long as your DFS Replication is working, the 'DO_NOT_REMOVE_NtFrs_PreInstall_Directory' should be empty soon.
It may just take a while, may be with lager file or quantity of files with the LAN/WAN links etc.

Now if your DFS is working, then your AD replication should work as well, I'll be surprise if it's not.

Author

Commented:
Thank you.  Sorry for the false alarm.

-Morgan
Access more of Experts Exchange with a free account
Thanks for using Experts Exchange.

Create a free account to continue.

Limited access with a free account allows you to:

  • View three pieces of content (articles, solutions, posts, and videos)
  • Ask the experts questions (counted toward content limit)
  • Customize your dashboard and profile

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.