Windows Server

Will · Guest

I'm finding that the file replication in Windows 2000 is fragile. It
breaks often. It is not reliable software. Unfortunately, Active
Directory replication seems to rely on file replication, so I need to
struggle and find a way to make it work.

How do you automate the testing of a file replication link to make sure the
replications are working? When I run DCDIAG /V I often see messages that
report replications to specific systems as failing, followed by the summary
line that the Replication test was passed. :) That doesn't give me much
confidence that anything works.

Are there any low cost network management tools that will test the health of
the system and report failures by e-mail immediately?

What is the best manual procedure to follow to diagnose in detail which
component of the file replication system is responsible for failures in
replication?

--
Will
Internet: westes AT earthbroadcast.com

Ren · Guest

Will:

AD replication does not rely on FRS at all.

They are two different things and mechanisms that only interact when FRS
queries AD to get configuration information.
That is the only things that goes on between these two components.

Make sure you don't confuse SYSVOL and DFS replication with AD replication.

SYSVOL and DFS replica sets are replicated by FRS.

AD is not!

Now, FRS works as is supposed either in Windows 2000 or above.
I agree with you that its fragile, but specially to bad configuration or
erroneous usage.

About the tools, you can try using SONAR or Ultrasound for monitoring.
These are tools from Microsoft, available for free at the following sites:

Sonar:
http://www.microsoft.com/windows2000/techinfo/reskit/tools/new/sonar-o.asp

UltraSound
http://www.microsoft.com/downloads/details.aspx?FamilyID=61acb9b9-c354-4f98-a823-24cc0da73b50&DisplayLang=en

FRS tools and settings
http://agent.microsoft.com/technet/prodtechnol/windowsserver2003/library/TechRef/3a94d321-4400-442f-a1a9-9569a0db2a56.mspx

You can also request the latest version of FRS to Microsoft, namely:

Windows 2000:

815473 File Replication Service Does Not Log Errors on Sharing Violations
http://support.microsoft.com/?id=815473

Windows 2003:

823230 Issues that are resolved in the pre-Service Pack 1 release of Ntfrs.exe
http://support.microsoft.com/?id=823230

Ultimately, you can find how the service works in detail at:

http://agent.microsoft.com/technet/prodtechnol/windowsserver2003/library/TechRef/965a9e1a-8223-4d3e-8e5d-39aeb70ec5d9.mspx

Hope it helps!

Cheers!

Ren

"Will" wrote:

Will · Guest

Thanks for clarifying that AD replication is different from FRS.

Regarding Ultrasound and Sonar: I'm a bit confused where these should be
running. The Ultrasound install wants an SQL Server, and if you install
MSDE version of SQL, you get a warning that Ultrasound and SQL Server
shouldn't be on the domain controller. Do I dedicate a machine as an FRS
network monitor?

In the Ultrasound interface, how do I simultaneously monitor four different
DCs in a root domain, and three child domains?

--
Will
Internet: westes AT earthbroadcast.com

"Ren" <Ren@discussions.microsoft.com> wrote in message
news:B4A57EE6-E189-43E5-BF21-DA383EC6BE2D@microsoft.com...

Paul Williams [MVP] · Guest

I've not got round to using ultrasound yet, so can't answer the second part
of your question, but as for the first...you can install it on your PC, or
on a server that performs roles such as SUS, SMS, or a general terminal
server that you use to administer all other servers, etc.

If you must, you can run it on a DC - depends on your environment size,
load, and available budget, etc.

--
Paul Williams
Microsoft MVP - Windows Server - Directory Services
http://www.msresource.net | http://forums.msresource.net

Best Practices for Testing File Replication and Keeping it R

	Windows Server Forum Index -> DFS and FRS	All times are GMT
Page 1 of 1