?
Solved

DFS stopped working after server restore

Posted on 2014-12-29
8
Medium Priority
?
2,342 Views
Last Modified: 2015-01-04
I recently restored a file server using a bare metal restore. On the surface all seemed well.

Days later I have noticed that DFS replication to another server is not functioning. There are no errors in either servers event logs. There are only 2 servers in the replication group.

Running a propagation test from either server results in the following error: (fs02 is the server that was restored)

Replication group Office Share, replicated folder Shared Folders on member fs02.xxx.local: A new propagation test file cannot be created. Cannot create propagation test folder under replicated  folder. Access is denied.


There are also errors and warnings in a health report:

This error was on the other server:
Inconsistent configuration detected (invalid object).  
  Affected replicated folders: All replicated folders on this server.
  Description: The DFS Replication service detected invalid msDFSR-Subscriber object data while polling for configuration information. Additional information includes Object DN: CN=8b791ae3-9f27-4b22-bdab-4eaf9a0111e1,CN=DFSR-LocalSettings,CN=WP-FS03,OU=Windows,OU=Servers,DC=xxx,DC=local Attribute Name: msDFSR-MemberReference and domain controller: WP-DC04.xxx.local. Event ID: 6002
  Last occurred: Monday, December 29, 2014 at 10:41:13 AM (GMT-5:00)


This warning on the restored server:

WARNINGS (There is 1 warning to report)
       
 Reference member returned no replicated folders.  
  Description: Backlog calculations cannot be performed because the reference member returned zero replicated folders.  
  Last occurred: Monday, December 29, 2014 at 11:29:23 AM (GMT-5:00)
  Suggested action: For information about troubleshooting backlog problems, see The Microsoft Web Site.  


It seems like a permissions issue, but im not sure what permissions need to be checked. I did find something strange though on the restored server. The permissions for the dfsrprivate folder matched the other server but the folder icons themselves show a lock over the folder. Also the staging folder and its subfolders size shows 0 bytes even though if you go into the subfolders, there are frx files with sizes greater then 0 bytes.
0
Comment
Question by:bts86
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 3
  • 2
8 Comments
 
LVL 79

Expert Comment

by:arnold
ID: 40522143
the error says it all.  you should use robocopy to make sure that there were no recently created files on the recently restored server that have been modified. If there were copy the ones that have changed to the "functional" member repeat for every share. file level backup of the share/s on the restored system.  Then using the non-restored member as a reference, reconfigure the DFS replication group for each share.  This should reset the referencing and replication will resume.
0
 
LVL 1

Author Comment

by:bts86
ID: 40522547
I backed up both server and re-synced data using a 3rd party program then deleted the replication group  and re-created it.

I am still getting the same errors when I run diagnostic reports and nothing copies between servers.
0
 
LVL 79

Expert Comment

by:arnold
ID: 40522650
A reset of the replication group is what will lead to the synchronization of the references.

There is also a lag time between the update of the DFS-R into the AD and when it is seen by the dfs-r members.

use dfs management and verify topology.

The errors will likely continue until the pre-existing files on both ends are rechecked.

The other option is often to remove one of the existing replication members. waiting for 20-30 minutes, and adding it back with one way replication from existing member to the newly added one.  Then revalidate topology to establish the two way communications.
When you see the errors in the diagnostic report does it deal with missing files from the existing to the recently restored, or the other way around, i.e. missing files from the restored not being copied to the member that was functional during the restore of the other.
0
Building an interactive eFuture classroom

Watch and learn how ATEN provided a total control system solution including seamless switching matrix switch, HDBaseT extenders, PDU, lighting control to build an interactive eFuture classroom.

 
LVL 1

Author Comment

by:bts86
ID: 40522673
Files are not being copied in either direction.

Right now I've removed one of the targets from its namespace so that I have everyone working on one server at least.

Ill give it some time and see if everything updates. If not, ill try re-adding the member I removed from the namespace as a one-way and see if it starts working.


Could it also be a bad entry in AD and could rejoining the servers to the domain be a possible fix?
0
 
LVL 79

Expert Comment

by:arnold
ID: 40522703
DFS has two components the published side that deals with the access. and the replication side that deals with keeping the two synchronized.


Remove the member that youjust restored from the replication group presumably you've already removed it from the published group.

Let the changes propagate tomorrow, check on the DFS tab in one of the clients to make sure this DFS is listing only the member/s that were not restored.
At this time, go through the replication group and add the recently restored member to the replication group with the existing member as the master against whom the contents would be validated.

if your OS is 2008 and newer, look at the dfsutil to resolve these errors if the above procedure does not resolve it.
0
 
LVL 1

Accepted Solution

by:
goldied earned 2000 total points
ID: 40523274
To try and completely reset your replication do the following:

Stop the dfsr (dfs replication service) on both machines.
open the system volume information folder on each drive containing dfs shares.
unhide system files and folders.
you should see a dfsr folder in here.
open command prompt and rename this folder from dfsr to dfsr2 and delete it.
(Repeat for all drives that contain shares being replicated).
If you have files and folders of different versions on both servers you'll now need to proceed in two ways:
Trash it all with what you think is the most up to date server.
Right a clever script to look at time stamps and synchronise all the data.

Once this is complete, restart the dfsr service and recreate your replication groups. Wait 15 minutes for initial replication.

If you want to check, look into the sysvol folder again and you should see all the dfsr db files changing and growing.
0
 
LVL 1

Expert Comment

by:goldied
ID: 40524665
Glad all went well , was it all smooth?
0
 
LVL 1

Author Comment

by:bts86
ID: 40530991
yes, it seemed the database was bad on the restored server. After it rebuilt itself, replication began to work again
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article summaries thoughts and ideas from two years of sustained use. It provides good reasoning to make the jump to Windows 10.
This article helps those who get the 0xc004d307 error when trying to rearm (reset the license) Office 2013 in a Virtual Desktop Infrastructure (VDI) and/or those trying to prep the master image for Microsoft Key Management (KMS) activation. (i.e.- C…
In this video, we discuss why the need for additional vertical screen space has become more important in recent years, namely, due to the transition in the marketplace of 4x3 computer screens to 16x9 and 16x10 screens (so-called widescreen format). …
This Micro Tutorial will give you a basic overview of Windows DVD Burner through its features and interface. This will be demonstrated using Windows 7 operating system.

771 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question