DFS does not replicate complete

  • Thread starter Thread starter Juergen Heckel
  • Start date Start date
J

Juergen Heckel

Hi,
I have a DFS replication between a W2k-SP4 DC and a W2k3 DC.
The first replica set (with 16 GB and 12000 files) replicates fine,
after one day all files are replicated and (in SONAR) backlogfiles are at 0.
The second replica set (with 4 GB and 55000 files) never comes to an
end: many files are not replicated on the target server, the
backlogfiles stay at 58000 on both servers over 3 days.
I tried deleting and reinstalling this second set, deleted the
frs-staging dir, increased the staging area size to 2 GB. I even tried a
"replicat set specific reinitialization" with the burflag D2, but all
without success.

Thanks for any info.
 
Hi Juergen-

Is the data you are replicating at a root for that DFS? In other words,
what is the path you use to reach that DFS?
 
Tim said:
Hi Juergen-

Is the data you are replicating at a root for that DFS? In other words,
what is the path you use to reach that DFS?
Click to expand...

Hi,
thanks for your answer, you are the first (in three newsgroups) :-)

the DFS root is on C:\, the links are on other drives (as E:\ and F:\).
But I tried even links on subdirectories on these drives. I can access
these links with \\heckel.jheckel.de\SYS5 where E:\ is shared as SYS5.

The first link runs fine, after some time the correspondig frs_staging
area is empty, but each other link (even with its own staging dir) does
never finish to replicate complete: either many files are missing or in
the staging dir there are >1000 files after 3 days.

SONAR shows with the "good" replication in the columns InJoin and
OutJoin a 1 for both servers, the bad ones show only a 1 in one InJoin
and one OutJoin column.
 
Hi Juergen-

From your description below it looks like you are enabling replication from
the root. We do not recomend this since it can lead to results like you are
seeing.

Instead it may help to create a DFS share on the root of
\\heckel.jheckel.de\SYS5, such as \\heckel.jheckel.de\SYS5\share1 . Then
create the links to the target shares for that location. If this is the
issue at hand the replication should be more consistent and smoother.

Please repost if this does not help or apply in your case.
 
Tim said:
From your description below it looks like you are enabling replication from
the root. We do not recomend this since it can lead to results like you are
seeing.
Click to expand...

Hi,
I read this suggestion but why does my first replication link work
perfectly? I had to shutdown the second DC for 3 days, after restarting
the server the (root-)replication startet too without problems.
Instead it may help to create a DFS share on the root of
\\heckel.jheckel.de\SYS5, such as \\heckel.jheckel.de\SYS5\share1 . Then
create the links to the target shares for that location. If this is the
issue at hand the replication should be more consistent and smoother.
Click to expand...
I tried this with two new links: the first one had the same problem as
already posted here, the second is OK.
Please repost if this does not help or apply in your case.
Click to expand...
I wanted to replicate two drives completely without changing a lot
(login scripts, shortcuts an so on). If this is not possible I have to
do it without DFS :-(

Is it possible to install the new DFSGUI (from W2k3) to W2k SP4?


Thanks.
 
Juergen said:
the DFS root is on C:\, the links are on other drives (as E:\ and F:\).
But I tried even links on subdirectories on these drives. I can access
these links with \\heckel.jheckel.de\SYS5 where E:\ is shared as SYS5.
Click to expand...

Hi,
sorry, my mappings are \\heckel.jheckel.de\DFS\SYS5.
 
Back
Top