RE: DFS-R: Data Wiped Out from Filestore Folder
- From: v-dashen@xxxxxxxxxxxxxxxxxxxx (David Shen [MSFT])
- Date: Wed, 05 Nov 2008 11:06:39 GMT
Hello Will,
According to my research, the expected behavior of the PreExisting folder
should be as followed:
When receiving files from the primary member during initial replication,
the receiving members that contain files that are not present on the
primary member should move these files to their respective
DfsrPrivate\PreExisting folder. Any updated or new files present on the
member will be moved to its own DfsrPrivate\PreExisting folder on the
member and will be replaced with authoritative files from another member.
Any local pre-existing content in this replicated folder that does not
exist on the primary member has been moved to the hidden system folder
DfsrPrivate\PreExisting under the replicated folder root.
Since the DfsrPrivate\PreExisting folder is an hidden system folder, could
you please modify the following folder option in Windows Explorer to check
if you can view the PreExisting folder respectively on the member server?
Windows Explorer -> Tools -> Folder Options -> View -> Show hidden files
and folders -> uncheck "Hide Protected operating system files"
If you cannot view the PreExisting folder under this circumstance, the
behavior of the problematic system seems to be unexpected.
Based on my test, when we add a member server into a current existing
replication group, the Primary member won't be assign automatically. So the
initial replication between the primary member and non-primary member won't
begin until we set primary member. In other words, the context in the
original replicated folder should not be wiped out.
Could you please follow the steps to check if the PreExisting folder can be
viewed.
Scenario:
Server1 (Replicated folder1)
Server2 (Replicated folder2)
Server1 and Server2 are the members of the replication group.
Steps:
1. Remove the Sever2 membership from the replication group.
2. Keep the content in Replicated folder1, and remove the content in
Replicate folder2
3. Add the Server2 to the replication group and the make the blank
replicated folder2 be the new replicated folder.
4. Manually set Server2 as the primary member by running following
Dfsradmin command.
Dfsradmin Membership Set /RGName:<replication group name>
/RFName:<replicated folder name> /MemName:<Server2> /IsPrimary:True
Please run Dfsrdiag pollad to trigger the synchronization with Active
Directory database.
5.if there is any conflict during the initial replication, it should have
content in the PreExisting Folder on the Server1.
6. in this case, there should be no PreExisting folder on Server2 because
the replicated folder2 is blank.
Hope it helps.
David Shen
Microsoft Online Partner Support
.
- Follow-Ups:
- RE: DFS-R: Data Wiped Out from Filestore Folder
- From: willk@newsgroup.nospam
- RE: DFS-R: Data Wiped Out from Filestore Folder
- Prev by Date: FILE_FLAG_BACKUP_SEMANTICS
- Next by Date: Re: How Move Roaming Profile Folder To New Drive
- Previous by thread: RE: DFS-R: Data Wiped Out from Filestore Folder
- Next by thread: RE: DFS-R: Data Wiped Out from Filestore Folder
- Index(es):
Relevant Pages
|
