ConflictAndDeleted files when not expecting there to be

I'm preparing our DFS setup to go live, but am trying to better understand
the ConflictandDeleted folder. We have a namespace "Files" that started out
with a single folder target. Then an additional folder target was added on a
different server in the same site, and the replication group auto-created.

However, the folder target on this second server was set to disabled so that
all users were still accessing the data on Server1. We are still getting 10's
of files being detected as Conflicting each day, which is odd since there's
only one available folder target.

Can someone perhaps give some explanation as to why this may be happening?

Hello Jadus01,

Although you said the second sever target is disabled, but my question,
after disabling was replication also disabled? It seems that eventhough file
is disabled, replication might be going on sp causing the conflict..To
better understand, on which server is the Conflict and Deleted folder
located/stored? This normally should be the server that resolved the
conflicts.

--
Isaac Oben [MCTIP:EA, MCSE]
"Jadus01" <> wrote in message
news:65016356-6A5F-4E26-8233-...
> I'm preparing our DFS setup to go live, but am trying to better understand
> the ConflictandDeleted folder. We have a namespace "Files" that started
> out
> with a single folder target. Then an additional folder target was added on
> a
> different server in the same site, and the replication group auto-created.
>
> However, the folder target on this second server was set to disabled so
> that
> all users were still accessing the data on Server1. We are still getting
> 10's
> of files being detected as Conflicting each day, which is odd since
> there's
> only one available folder target.
>
> Can someone perhaps give some explanation as to why this may be happening?

No, replication is not disabled. Our intent is that Server2 will eventually
be moved to a branch office, so right now we are making sure all data has
been replicated, but not changing on Server2. There are Conflict folders on
both servers, but the one with most files is on Server2 (one with disabled
folder target).

These conflicts are unexpected to me because I thought a conflict happened
when a file was changed on both servers, where DFSR then has to replicate the
most current. With the folder target being disabled on Server2, there should
be no changes there, and therefore no conflict.

"Isaac Oben [MCITP,MCSE]" wrote:

> Hello Jadus01,
>
> Although you said the second sever target is disabled, but my question,
> after disabling was replication also disabled? It seems that eventhough file
> is disabled, replication might be going on sp causing the conflict..To
> better understand, on which server is the Conflict and Deleted folder
> located/stored? This normally should be the server that resolved the
> conflicts.
>
> --
> Isaac Oben [MCTIP:EA, MCSE]
> "Jadus01" <> wrote in message
> news:65016356-6A5F-4E26-8233-...
> > I'm preparing our DFS setup to go live, but am trying to better understand
> > the ConflictandDeleted folder. We have a namespace "Files" that started
> > out
> > with a single folder target. Then an additional folder target was added on
> > a
> > different server in the same site, and the replication group auto-created.
> >
> > However, the folder target on this second server was set to disabled so
> > that
> > all users were still accessing the data on Server1. We are still getting
> > 10's
> > of files being detected as Conflicting each day, which is odd since
> > there's
> > only one available folder target.
> >
> > Can someone perhaps give some explanation as to why this may be happening?
>

Hello

Read more about that here:
http://technet.microsoft.com/en-us/l.../cc782648.aspx

Hope this helps,

--
Isaac Oben [MCTIP:EA, MCSE]
"Jadus01" <> wrote in message
news:EEF1A0F0-F0D7-4464-BD62-...
> No, replication is not disabled. Our intent is that Server2 will
> eventually
> be moved to a branch office, so right now we are making sure all data has
> been replicated, but not changing on Server2. There are Conflict folders
> on
> both servers, but the one with most files is on Server2 (one with disabled
> folder target).
>
> These conflicts are unexpected to me because I thought a conflict happened
> when a file was changed on both servers, where DFSR then has to replicate
> the
> most current. With the folder target being disabled on Server2, there
> should
> be no changes there, and therefore no conflict.
>
> "Isaac Oben [MCITP,MCSE]" wrote:
>
>> Hello Jadus01,
>>
>> Although you said the second sever target is disabled, but my question,
>> after disabling was replication also disabled? It seems that eventhough
>> file
>> is disabled, replication might be going on sp causing the conflict..To
>> better understand, on which server is the Conflict and Deleted folder
>> located/stored? This normally should be the server that resolved the
>> conflicts.
>>
>> --
>> Isaac Oben [MCTIP:EA, MCSE]
>> "Jadus01" <> wrote in message
>> news:65016356-6A5F-4E26-8233-...
>> > I'm preparing our DFS setup to go live, but am trying to better
>> > understand
>> > the ConflictandDeleted folder. We have a namespace "Files" that started
>> > out
>> > with a single folder target. Then an additional folder target was added
>> > on
>> > a
>> > different server in the same site, and the replication group
>> > auto-created.
>> >
>> > However, the folder target on this second server was set to disabled so
>> > that
>> > all users were still accessing the data on Server1. We are still
>> > getting
>> > 10's
>> > of files being detected as Conflicting each day, which is odd since
>> > there's
>> > only one available folder target.
>> >
>> > Can someone perhaps give some explanation as to why this may be
>> > happening?
>>

That article just re-inforces my confusion. It says, "DFS Replication uses a
"last-writer wins" method for determining which version of a file to keep
when a file is modified on two or more members. The losing file is stored in
the Conflict and Deleted folder."

These files aren't being modified on two members though, since one of the
targets is disabled. So somehow conflicts are being detected when changes are
made on only one member.

I did noticed that the antivirus software on these servers weren't excluding
the DFSRoot folder, which I have since changed. I imagine that could possibly
cause this behaviour.

"Isaac Oben [MCITP,MCSE]" wrote:

> Hello
>
> Read more about that here:
> http://technet.microsoft.com/en-us/l.../cc782648.aspx
>
> Hope this helps,
>
> --
> Isaac Oben [MCTIP:EA, MCSE]
> "Jadus01" <> wrote in message
> news:EEF1A0F0-F0D7-4464-BD62-...
> > No, replication is not disabled. Our intent is that Server2 will
> > eventually
> > be moved to a branch office, so right now we are making sure all data has
> > been replicated, but not changing on Server2. There are Conflict folders
> > on
> > both servers, but the one with most files is on Server2 (one with disabled
> > folder target).
> >
> > These conflicts are unexpected to me because I thought a conflict happened
> > when a file was changed on both servers, where DFSR then has to replicate
> > the
> > most current. With the folder target being disabled on Server2, there
> > should
> > be no changes there, and therefore no conflict.
> >
> > "Isaac Oben [MCITP,MCSE]" wrote:
> >
> >> Hello Jadus01,
> >>
> >> Although you said the second sever target is disabled, but my question,
> >> after disabling was replication also disabled? It seems that eventhough
> >> file
> >> is disabled, replication might be going on sp causing the conflict..To
> >> better understand, on which server is the Conflict and Deleted folder
> >> located/stored? This normally should be the server that resolved the
> >> conflicts.
> >>
> >> --
> >> Isaac Oben [MCTIP:EA, MCSE]
> >> "Jadus01" <> wrote in message
> >> news:65016356-6A5F-4E26-8233-...
> >> > I'm preparing our DFS setup to go live, but am trying to better
> >> > understand
> >> > the ConflictandDeleted folder. We have a namespace "Files" that started
> >> > out
> >> > with a single folder target. Then an additional folder target was added
> >> > on
> >> > a
> >> > different server in the same site, and the replication group
> >> > auto-created.
> >> >
> >> > However, the folder target on this second server was set to disabled so
> >> > that
> >> > all users were still accessing the data on Server1. We are still
> >> > getting
> >> > 10's
> >> > of files being detected as Conflicting each day, which is odd since
> >> > there's
> >> > only one available folder target.
> >> >
> >> > Can someone perhaps give some explanation as to why this may be
> >> > happening?
> >>
>

Just an update, we haven't had any conflicting files since the antivirus
exclusion rules were modified yesterday. It appears that was the problem.

"Jadus01" wrote:

> That article just re-inforces my confusion. It says, "DFS Replication uses a
> "last-writer wins" method for determining which version of a file to keep
> when a file is modified on two or more members. The losing file is stored in
> the Conflict and Deleted folder."
>
> These files aren't being modified on two members though, since one of the
> targets is disabled. So somehow conflicts are being detected when changes are
> made on only one member.
>
> I did noticed that the antivirus software on these servers weren't excluding
> the DFSRoot folder, which I have since changed. I imagine that could possibly
> cause this behaviour.
>
> "Isaac Oben [MCITP,MCSE]" wrote:
>
> > Hello
> >
> > Read more about that here:
> > http://technet.microsoft.com/en-us/l.../cc782648.aspx
> >
> > Hope this helps,
> >
> > --
> > Isaac Oben [MCTIP:EA, MCSE]
> > "Jadus01" <> wrote in message
> > news:EEF1A0F0-F0D7-4464-BD62-...
> > > No, replication is not disabled. Our intent is that Server2 will
> > > eventually
> > > be moved to a branch office, so right now we are making sure all data has
> > > been replicated, but not changing on Server2. There are Conflict folders
> > > on
> > > both servers, but the one with most files is on Server2 (one with disabled
> > > folder target).
> > >
> > > These conflicts are unexpected to me because I thought a conflict happened
> > > when a file was changed on both servers, where DFSR then has to replicate
> > > the
> > > most current. With the folder target being disabled on Server2, there
> > > should
> > > be no changes there, and therefore no conflict.
> > >
> > > "Isaac Oben [MCITP,MCSE]" wrote:
> > >
> > >> Hello Jadus01,
> > >>
> > >> Although you said the second sever target is disabled, but my question,
> > >> after disabling was replication also disabled? It seems that eventhough
> > >> file
> > >> is disabled, replication might be going on sp causing the conflict..To
> > >> better understand, on which server is the Conflict and Deleted folder
> > >> located/stored? This normally should be the server that resolved the
> > >> conflicts.
> > >>
> > >> --
> > >> Isaac Oben [MCTIP:EA, MCSE]
> > >> "Jadus01" <> wrote in message
> > >> news:65016356-6A5F-4E26-8233-...
> > >> > I'm preparing our DFS setup to go live, but am trying to better
> > >> > understand
> > >> > the ConflictandDeleted folder. We have a namespace "Files" that started
> > >> > out
> > >> > with a single folder target. Then an additional folder target was added
> > >> > on
> > >> > a
> > >> > different server in the same site, and the replication group
> > >> > auto-created.
> > >> >
> > >> > However, the folder target on this second server was set to disabled so
> > >> > that
> > >> > all users were still accessing the data on Server1. We are still
> > >> > getting
> > >> > 10's
> > >> > of files being detected as Conflicting each day, which is odd since
> > >> > there's
> > >> > only one available folder target.
> > >> >
> > >> > Can someone perhaps give some explanation as to why this may be
> > >> > happening?
> > >>
> >

Jadus01

Good to know and thanks for sharing!

--
Isaac Oben [MCTIP:EA, MCSE]
"Jadus01" <> wrote in message
news:F3F3AC5F-6034-4D14-95A7-...
> Just an update, we haven't had any conflicting files since the antivirus
> exclusion rules were modified yesterday. It appears that was the problem.
>
> "Jadus01" wrote:
>
>> That article just re-inforces my confusion. It says, "DFS Replication
>> uses a
>> "last-writer wins" method for determining which version of a file to keep
>> when a file is modified on two or more members. The losing file is stored
>> in
>> the Conflict and Deleted folder."
>>
>> These files aren't being modified on two members though, since one of the
>> targets is disabled. So somehow conflicts are being detected when changes
>> are
>> made on only one member.
>>
>> I did noticed that the antivirus software on these servers weren't
>> excluding
>> the DFSRoot folder, which I have since changed. I imagine that could
>> possibly
>> cause this behaviour.
>>
>> "Isaac Oben [MCITP,MCSE]" wrote:
>>
>> > Hello
>> >
>> > Read more about that here:
>> > http://technet.microsoft.com/en-us/l.../cc782648.aspx
>> >
>> > Hope this helps,
>> >
>> > --
>> > Isaac Oben [MCTIP:EA, MCSE]
>> > "Jadus01" <> wrote in message
>> > news:EEF1A0F0-F0D7-4464-BD62-...
>> > > No, replication is not disabled. Our intent is that Server2 will
>> > > eventually
>> > > be moved to a branch office, so right now we are making sure all data
>> > > has
>> > > been replicated, but not changing on Server2. There are Conflict
>> > > folders
>> > > on
>> > > both servers, but the one with most files is on Server2 (one with
>> > > disabled
>> > > folder target).
>> > >
>> > > These conflicts are unexpected to me because I thought a conflict
>> > > happened
>> > > when a file was changed on both servers, where DFSR then has to
>> > > replicate
>> > > the
>> > > most current. With the folder target being disabled on Server2, there
>> > > should
>> > > be no changes there, and therefore no conflict.
>> > >
>> > > "Isaac Oben [MCITP,MCSE]" wrote:
>> > >
>> > >> Hello Jadus01,
>> > >>
>> > >> Although you said the second sever target is disabled, but my
>> > >> question,
>> > >> after disabling was replication also disabled? It seems that
>> > >> eventhough
>> > >> file
>> > >> is disabled, replication might be going on sp causing the
>> > >> conflict..To
>> > >> better understand, on which server is the Conflict and Deleted
>> > >> folder
>> > >> located/stored? This normally should be the server that resolved the
>> > >> conflicts.
>> > >>
>> > >> --
>> > >> Isaac Oben [MCTIP:EA, MCSE]
>> > >> "Jadus01" <> wrote in message
>> > >> news:65016356-6A5F-4E26-8233-...
>> > >> > I'm preparing our DFS setup to go live, but am trying to better
>> > >> > understand
>> > >> > the ConflictandDeleted folder. We have a namespace "Files" that
>> > >> > started
>> > >> > out
>> > >> > with a single folder target. Then an additional folder target was
>> > >> > added
>> > >> > on
>> > >> > a
>> > >> > different server in the same site, and the replication group
>> > >> > auto-created.
>> > >> >
>> > >> > However, the folder target on this second server was set to
>> > >> > disabled so
>> > >> > that
>> > >> > all users were still accessing the data on Server1. We are still
>> > >> > getting
>> > >> > 10's
>> > >> > of files being detected as Conflicting each day, which is odd
>> > >> > since
>> > >> > there's
>> > >> > only one available folder target.
>> > >> >
>> > >> > Can someone perhaps give some explanation as to why this may be
>> > >> > happening?
>> > >>
>> >