RE: DFS-R: Data Wiped Out from Filestore Folder



David,

Sorry, I've been misunderstanding the usage of the ConflictAndDeleted
folder. It's the PreExisting folder I should have been talking about.

However, the big question over what happened to my data still remains. There
is no PreExisting folder on the server!

The files seem to have simply vanished.

I really need to know why this happened. I have worked with DFS-R in the
past when it moved files into the PreExisting folder this was a safety catch
to ensure the data wasn't lost.

Please help to explain why the files were not moved into the PreExisting
folder. Again, I appreaciate your time taken to answer these questions.



Will



"David Shen [MSFT]" wrote:

Hello Will,

Thanks for the reply.

According to the further research, here is some information which is
helpful for you.

Analysis and Suggestion:
==========================

Primary Server only take effect during the initial replication. When we
performed initial replication, the primary server has the PRIMARY flag. The
replicated folder state in the internal DFS Replication database of primary
server is set to initial-primary; meanwhile, the replicated folder state in
the internal DFS Replication database of all other non-primary server is
set to initial-sync-needed. After initial replication, the downstream
partner will change the state to Normal. Please note that when the primary
member replicates with one of its upstream partners, initially it will not
get any data from them (since they will be in initial-sync-needed state).
Once the replicated folder on the upstream member changes to normal state,
the primary member can receive the replicated data (hopefully mostly
unchanged, if there have been no changes on the other members after the
data was replicated in to those members). At this point, the replicated
folder state on the primary member will also change to normal. In other
words, the primary member is no longer special for that replicated folder;
it is just another member in the system. DFS Replication on the designated
primary member will clear the primary flag in Active Directory for that
replicated folder, by setting the primary flag in Active Directory to 0 for
the relevant subscription object.

This is to say, once the initial replication has completed and the primary
server has received the replication from other server, its primary flag
will be removed. In this case, since the initial replication has been
completed within the replication group, no server will be listed as primary
member after you run the command line.

dfsradmin membership list /rgName:MyReplicationGroup
/attr:MemName,isPrimary IsPrimary

Concerning the question of ConfilctandDeleted folder, every member server
has its own ConflictandDeleted folder. Assuming that Server1 receives files
from the primary member Server2 during initial replication, the receiving
members that contain files that are not present on the primary member will
move those files to their respective DfsrPrivate\PreExisting folder. If a
file is identical to a file on the primary member, the file is not
replicated. If the version of a file on the receiving member Server1 is
different from the version of the primary member server2, the version of
the receiving member is moved to the ConflictandDeleted folder and RDC can
be used to download only the changed blocks. As there are no files in the
new member server, there is no conflicts and no files are moved to the
"ConflictandDeleted" folder.

Hope the explanation is helpful for you.

David Shen
Microsoft Online Partner Support


.



Relevant Pages

  • MS Exchange 2000 umziehen
    ... level folder have a replica on the target server. ... public folder replication messages are low ...
    (microsoft.public.de.german.exchange2000.general)
  • RE: reomve server from site.
    ... How to Remove the First Exchange 2000 Server Computer from the Site ... the Offline Address Book folder, the Schedule+ Free Busy folder, the Events ... Click the Replication tab, and then click Add. ...
    (microsoft.public.exchange2000.admin)
  • Re: Public Folder replication still occurring after removing replica
    ... still attempting to replicate between the old & the new server). ... I set up the replication according to 307917. ... folders & OAB Version2 still listed under Public Folder Instances. ...
    (microsoft.public.exchange.admin)
  • Re: Public folder replication 5.5 -> E2K3 not working correctly
    ... Confirm that there are replicas on both the 5.5 and the 2003 server. ... open the folder in question with Outlook. ... > second box to E2K3. ... I've tried sending the replication request ...
    (microsoft.public.exchange2000.admin)
  • RE: DFS-R: Data Wiped Out from Filestore Folder
    ... Server 2003 R2 or Windows Server 2008? ... What is the size of the replicated folder that you encounter the issue? ... Are the replicated folders same in size on the 2 DFS-R member server before ... When you join a server to be a member of the current replication group ...
    (microsoft.public.windows.file_system)