Hi,
whats the best way to add a new target to Namespace and replication. Goal is to replace a old file Server at the end.
I did the following:
- copied the share with robocopy incl timestamps of files and folders
- created share
- added the new share as a new target as well as meshd member of the replication connection
- disabled the new member in the Namespace, so no one can Access it until dfsr is fully done and initialized
After the the new dfsr Connection was replicated through AD to all 4 Members (3 different site, 1 same site) the
following happend:
dfsr begin and almost every file was in a conflicted and copied over the the Conflict Folder. Almost all timestamps
of the Folders were changed to the current date, but the timestamps of the files not.
Thousands of eventlogs: 4412
The DFS Replication service detected that a file was changed on multiple servers. A conflict resolution algorithm was used to determine the winning file. The losing file was moved to the Conflict and Deleted folder.
Any idea why? Later on i disabled the Connections to the remote Fileservers, but that did not stop it.
My idea was to pre-seed the files with robocopy. So what would be the best way to prevent that for the next share ? Is it a better way to just add the target to a bi-directional Connection to the local Fileserver without adding to DFS-N and without copying
the files before ? Is it better to let DFSR do the hole Initial sync incl Files ?
At the end i have no loss of date but to check almost every file for conflict took Ages to finish.
Thanks a lot,
Marco