Re: DFS Replication Topology



Hello Lee,

You should better post in:
microsoft.public.windows.server.dfs_frs

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

I will look for some logs but for now here is more clarification:

Our DFS setup at DJJ is as follows:

A. We have one replication group for each yard server (currently
around 50 groups). These groups individually collect .jpgs as they
are generated at the local yard and replicates them back to the
central server in Cincinnati. Once there, an application consumes the
.jpgs and removes them from the DFS share on the central server. That
"deletion" replicates back to the yard servers to keep them clean of
the now unneeded .jpgs.

B. We also have a replication group that replicates documentation and
application install files that our group uses from the central server
in Cincinnati down to each yard server. In this manner we are always
able to locally access needed applications and documents within our
group.

C. Finally, we have one replication group for each LLC that DJJ owns
(five of them currently). These groups are responsible for
replicating data between the individual yard servers, the LLC HQ
location and the central server in Cincinnati (for backup purposes).
The files in question are documents that management at the LLC HQ and
at each yard within the LLC needs for day-to-day business. The
replication occurs only within each LLC's replication group. The file
hierarchy, at the root level, is identical for each LLC's replication
folder group, however, the individual documents are not.

Problems:
1. We have a user whose laptop, according to him, is constantly being
referred to a different DFS server share. I'm not sure why he's
checking
this multiple times throughout the day, but I suppose that when he
notices a
particular document is slow to load and/or save, he checks his DFS
server
referral list to see where he's pointing. We've run Microsoft's
"WindowsXP-KB898900-v2-x86-ENU.exe" hotfix which has resolved this
problem in
everyone's PC, except his.
2. From time to time users report that changes they made to a
particular document the night before are not showing up the next
morning. Most of these turn out to be two people editing the same
document at the same time and we can find the "missing changes" in the
"ConflictsandDeleted" folder. But there have been a time or two where
no such file exists and I'm left to wonder if there are other things
to try in troubleshooting.

3. Permissions and replication. We haven't had too much trouble with
this, but it seems that sometimes security settings on folders and
documents do not always replicate.

4. There have been two occasions where replication between one yard
server (in setup C above) and all other servers in the group ceases.
No error messages are generated in a diagnostic report and the error
logs do not indicate any problems. But nothing replicates to or from
that share. Recreating that share from scratch has so far proven to
be the only way to fix it.

"Meinolf Weber" wrote:

Hello Lee,

Do you get any errors, or how did you recognize it? Event viewer
errors, then post the error here? Please be more specific.

Also you can check with dfsutil you replication:
http://technet2.microsoft.com/windowsserver/en/library/ae08acaa-148d-
41eb-a693-35d80c4590751033.mspx?mfr=true
http://technet2.microsoft.com/windowsserver/en/library/67eefef1-65fb-
47f1-a40d-2aa7c46922e91033.mspx?mfr=true

http://technet2.microsoft.com/windowsserver/en/library/06894c4e-aff0-
4966-b794-e160839c3ce81033.mspx?mfr=true

http://technet2.microsoft.com/windowsserver/en/library/28be5bc5-694d-
49ea-981e-34bdadd1a9311033.mspx?mfr=true

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and
confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
I am experiencing an issue where a server is dropping out of my
replication topology for DFS.

Currently we have DFS up and running. We have 8 Limited Liability
Companies We have a Headquarters and the LLC is a mesh with one
bridgehead and one of the LLC. We have a Hub and Spoke topology and
are using Windows Server 2003 R2.

DFS was setup in its default configuration initially and no further
configurations were done.



.



Relevant Pages

  • Re: SBS 2003 and Replication Errors with Remote DC
    ... I just promoted the remote DC last week, so I still have time to solve the replication issues. ... Domain Controller Diagnosis ... Connecting to directory service on server alpha. ... Performing upstream analysis. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 and Replication Errors with Remote DC
    ... alpha server as soon as you can to get things going. ... A simple DNS replication test is to create a host record in the SBS server ... Domain Controller Diagnosis ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 and Replication Errors with Remote DC
    ... I did make the changes that you suggested on the DNS of my alpha server and rebooted. ... I did run the simple DNS test that you suggested by adding a host record to my SBS server. ... A simple DNS replication test is to create a host record in the SBS server and wait till it shows up in the remote server. ...
    (microsoft.public.windows.server.sbs)
  • Re: DC Query
    ... (Unless you have replication going, I haven't look at the article kj came up ... > server just for the data, it had to stay on the first DC. ... > approach them with this idea until I knew DFS could cope with disk quotas ...
    (microsoft.public.windows.server.active_directory)
  • Re: Unable to decommission a Windows 2008 DC via dcpromo
    ... Can you open and compare sysvol and netlogon share on both DCs? ... Verifying that the local machine server2, ... The File Replication Service Event log test ... Latency information for 8 entries in the vector were ...
    (microsoft.public.windows.server.active_directory)