Replication Process - Files are deleted during process
Windows Server Forum Index Windows Server
Server discussion on Windows platform.
 
 FAQFAQ   MemberlistMemberlist     RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 
 
Google
 
Web winserverhelp.com
Replication Process - Files are deleted during process

 
Post new topic   Reply to topic    Windows Server Forum Index -> DFS and FRS
Author Message
JoeC
Guest





Posted: Mon Nov 22, 2004 11:49 pm    Post subject: Replication Process - Files are deleted during process Reply with quote

We have noticed with FRS that when a file is replicated between two servers
(I will call the "FROM" location the "Master" and the "TO" location the
"Recipient") the File in the Master Location is retained throughout and the
one in the Recipient location is temporarily deleted before being updated.
Now depending on file size and WAN speed (2MB Leased line) the Recipient
location can be missing its file from some time.

Should a user go to access the file during this time the DB trying to locate
it at the Recipient location cannot and therefore creates and opens a new
blank file. thus effectively wiping the original!

Can FRS be set to leave the file being replicated in the Recipient location
until it needs to overwrite it hence the Recipient location is NEVER missing
the File?

Many thanks

JC
Back to top
Richard Chinn [MSFT]
Guest





Posted: Tue Nov 23, 2004 12:04 pm    Post subject: Re: Replication Process - Files are deleted during process Reply with quote

There is no way to have FRS changes on a "master" always win over
changes on a "recipient." This is because FRS is a multi-master
replication system. This means that all machines are both "masters"
and "recipients."

As this is the case, FRS must perform conflict resolution to determine
when conflicting changes (the one you describe is a basic case of a
conflict) are detected. In general, FRS uses last writer wins
semantics, so this is why your last-written, blank file is overwriting
the original file.

If you are using your setup in a publication scenario (data is created
and modified on one machine, then sent out to other machines where
it's only read), you could have your second server share its data as
read-only. This would prevent an application from creating the blank
file on the machine that will win over the original.

--Richard

Please post FRS related questions to
microsoft.public.windows.server.dfs_frs and prefix the subject line
with "FRS:" to make it easier to spot. Note that FRS is used to
replicate SYSVOL on domain controllers and DFS root and link targets.

For additional FRS resources, please visit
http://www.microsoft.com/frs.

This posting is provided "AS IS" with no warranties, and confers no
rights.

On Mon, 22 Nov 2004 09:49:02 -0800, "JoeC"
<JoeC@discussions.microsoft.com> wrote:

Quote:
We have noticed with FRS that when a file is replicated between two servers
(I will call the "FROM" location the "Master" and the "TO" location the
"Recipient") the File in the Master Location is retained throughout and the
one in the Recipient location is temporarily deleted before being updated.
Now depending on file size and WAN speed (2MB Leased line) the Recipient
location can be missing its file from some time.

Should a user go to access the file during this time the DB trying to locate
it at the Recipient location cannot and therefore creates and opens a new
blank file. thus effectively wiping the original!

Can FRS be set to leave the file being replicated in the Recipient location
until it needs to overwrite it hence the Recipient location is NEVER missing
the File?

Many thanks

JC
Back to top
 
Post new topic   Reply to topic    Windows Server Forum Index -> DFS and FRS All times are GMT
Page 1 of 1

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum




New Topics Powered by phpBB