It sounds like you're replicating the root of your namespace (i.e., you
enabled replication directly on the root). This is something we recommend
against for several reasons (below). What you need to do is enable
replication on individual links, which will sync the data among the targets
of the link. I also highly recommend using Ultrasound and reviewing the
resources at www.microsoft.com/frs.
If upgrading to Windows Server 2003 R2 is an option, please consider doing
so. The new replication engine in R2, called DFS Replication, is more robust
and scalable than FRS.
From the DFS FAQ at
Q. If I use multiple root targets in a domain-based DFS namespace, do I need
to enable replication on the root?
A. No. DFS takes care of creating the necessary folder structures on each
root target. In fact, we recommend against enabling replication on the root,
although this step is sometimes done so that data stored in multiple root
folders stays synchronized. Instead, it is better to store data in link
targets and enable replication on links for the following reasons.
. When you enable replication on the root, morphed folders can occur under
the DFS root folder. Morphed folders occur when two or more identically
named folders on different servers are added to the replica tree. FRS
identifies the conflict during replication, and the receiving member
protects the original copy of the folder and renames (morphs) the later
inbound copy of the folder. The morphed folder names have a suffix of
"_NTFRS_xxxxxxxx" where "xxxxxxxx" represents eight random hexadecimal
Morphed folders occur in replicated roots for the following reason: When you
create a link in the namespace, DFS creates a link folder under each root
folder on every root server. For example, if you add 1,000 links to a
namespace, DFS creates a link folder under the DFS root folder for each of
those 1,000 links on every root server. When you enable FRS replication on
the root, FRS attempts to replicate its local copy of the folder structure
to every root server. Because each root server has a local copy of the same
folder structure as the incoming changes, FRS identifies the duplicate
folder names and renames the folders that were most recently created. FRS
then replicates all morphed folders to all root targets in the replica set.
. When adding a new root target to an FRS replicated root, you cannot
replicate the contents of individual folders in the root based on business
priority. Instead, the entire contents of the root are replicated to the new
root target. However, if you enable replication only on individual links,
you are creating multiple replica sets, which allows you to enable
replication on the most important links first, and then enable replication
on the links in the namespace as desired.
. You cannot take individual root targets offline. For example, if you are
adding a new root target, users who are referred to the new member might see
incomplete data until replication is complete. However, if you enable
replication on individual links, you can take a new link target offline
while the initial replication takes place or whenever you want to restrict
access to a particular link target.
This posting is provided "AS IS" with no warranties, and confers no rights.
Want to learn more about Windows Server file and storage technologies? Visit
our team blog at http://blogs.technet.com/filecab/default.aspx.
Post by scottjamez
Hello, Thanks in advance to anyone who can assist me with a rather
We currently have 1 W2k3 DC that is also our main file server. I just
added a 2nd W2k3 Server and set it up as a DC also. The replication of
AD information seems to be working fine (I can down server1 and server2
will still authenticate logins).
I set up a Domain DFS Root on Server1 by creating a Root Target for
that server name with about 10 links to different shares on that same
server. I then added Server2 and made it a DC. I made another Root
Target for that server. I ran the replication wizard and chose the
Ring topology. I left the defaults for the staging areas.
My DFS has both servers listed and all links listed on each server.
The ammount of data in total, between all of the shares on Server1 is
about 75 GB. The location with the shared directory and the links for
the DFS on Server2 has over 1 TB of free storage.
I set up the replication but there are no files being "replicated" to
Server2 (at least none that I can see).
If I go to \\domain\shares i see all my data. I see the Identical data
if I look at \\server1\shares or \\server2\shares.
I need to have the same data on both file servers and have a
replication schedule set up for off hours. For right now the
replication schedule is set to be 24/7.
To sum up my question, "Where is my data on Server2"?