DFS replication and the folder Ntfrs_PreExisting folders

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

We have 3 2k servers 2 are domain controllers and 1 isnt. We run a AD 2k
schema with some 2k3 servers. I setup the DFS through a 2k3 server MMC to
the 2k servers. I set the 3 servers as domain roots to a share locally on
each server. This share is the users home drives and TS profiles. 1 server
has all the data the other 2 dont. At first the replication was ok and
everything was fine. The 2 servers that didnt have the files it replicated
over the files with no problems. About 1 hour or so after it finished is
when I had problems.

Now upon file changes a second replication takes place. I keep getting
event ID 13520 and the Ntfrs_PreExisting folders pop up. Upon this happening
nobody can access their home drives as they are not in the current locations.
It goes into a complete replication instead of just changes.

I have no links or target created in the DFS roots. Am I doing something
wrong here? If so how should I create this? Why do I keep getting
Ntfrs_PreExisting folder?
 
No restore of AD was done. The SYSVOl/domain name has scripts, policies
directories in it and also a DO_NOT_REMOVE_NTFRS_PreExisting folder in it.
 
Ok after 5 days of wracking my head I cant figure this out. Anytime I try to
create a DFS share and make 2 servers the target root for the links I keep
getting this Pre_existing folder. This takes all my data and dumps it in
this type of directory after I set up replication. I cant move no data out
this folder to put it back. both server are domain controllers and are in
sync with other DC's. Its only when I make a dfs share that this happens.

Can a dfs share have 2 target roots for the same links?
 
I have 2 servers both DC's. I created a DFS share and created 2 links to 2
network shares. Now I need these 2 shares replicated to another server. So
I created 2 targets to the server I need them replicated to.

Now my problem is everything I do I get the NTFRS_PreExisting__See event
viewer folder. This takes everything into it and never comes back. I cant
copy/move it back or even xcopy it back.

At first I get event ID 13553 and 13554 saying they added to the frs.

Then I get event ID 13508

The File Replication Service is having trouble enabling replication from
ABDRSDC to ABPRO*** for e:\tusers using the DNS name abdrsdc.****.local. FRS
will keep retrying.
Following are some of the reasons you would see this warning.

[1] FRS can not correctly resolve the DNS name abdrsdc.****.local from this
computer.
[2] FRS is not running on abdrsdc.****.local.
[3] The topology information in the Active Directory for this replica has
not yet replicated to all the Domain Controllers.

This event log message will appear once per connection, After the problem
is fixed you will see another event log message indicating that the
connection has been established.


I had let the server sit for 24 hours and nothing. No replication takes
place. I can ping both from each other, do tracerts, nslookups and even map
drives to one other. DCdiag and netdiag show no errors and they both pass
all tests.

After I while I get event ID 13509 on the target server I need the shares
replicated

The File Replication Service has enabled replication from ABPROFILES to
ABDRSDC for e:\drtsprofiles after repeated retries.

Nothing happens after that due to the fact everything is sitting in the
NTFRS_PreExisitng folder.

This is where I am stumped. I been at this for a week and rebuilt the and
renamed the server many times and I get the same issues.
 
Back
Top