Dear Microsoft;

There is a SERIOUS problem between FRS and your defrag
APIs in Windows 2000 Server. Defrag utilities "fight" with
file replication. Moving a file during defrag SHOULD NOT
trigger FRS. You know about this:
{http://support.microsoft.com/default.aspx?scid=kb;en-
us;282791}. And my sources suggest you've known about it
long before this KB article was published.

If "excessive FRS replication traffic" were the only
effect of this issue, it would be a serious anoyance. But
under certain circumstances DATA LOSS CAN OCCUR. If a file
is changed on server A, while a defrag is taking place on
server B (and they are linked by FRS), FRS can see the
defragged file as being *newer* than the newly changed
file -- overwriting the new data on server A with old data
on server B. THIS IS A REAL PROBLEM, and because FRS can
be seriously slow when swamped with a lot of replication
(such as false replication triggered by a defrag)
the "window of opportunity" can be several hours wide.

I can accept that FRS is a minimal utility with a limited
set of circumstances where it is useful. But what I cannot
accept is that this issue can lead to data loss.

Loosing changes to Active Directory data sucks. Loosing
changes to user data sucks. Fix the stinkin problem
already. This SHOULD have been fixed back with SP-2 (or
shortly thereafter). This is a CRITICAL issue, it should
be handled as such through Windows Update. Even with the
release of Windows 2003 Server, you'll be supporting
Windows 2000 Server for the next three or four years to
come.

So how about some support. PLEASE FIX THIS!!!!

Thank you.

ScottyDM

Dear ScottyDM:

Yes there was a problem with with marking handles in the defrag API on
Windows 2000 which have since fixed in SP3. What version of Windows 2000
are you using? I would also recommend that you get the latest FRS QFE for
Windows 2000 SP3 Q815473 which has several fixes and enhancements. You can
call PSS and obtain it.

Please post again if this issue has not been resolved with a more recent
service pack.

Thanks,
Shobana

"ScottyDM" <(E-Mail Removed)> wrote in message
news:0d7001c37dd4$58290d50$(E-Mail Removed)...
> Dear Microsoft;
>
> There is a SERIOUS problem between FRS and your defrag
> APIs in Windows 2000 Server. Defrag utilities "fight" with
> file replication. Moving a file during defrag SHOULD NOT
> trigger FRS. You know about this:
> {http://support.microsoft.com/default.aspx?scid=kb;en-
> us;282791}. And my sources suggest you've known about it
> long before this KB article was published.
>
> If "excessive FRS replication traffic" were the only
> effect of this issue, it would be a serious anoyance. But
> under certain circumstances DATA LOSS CAN OCCUR. If a file
> is changed on server A, while a defrag is taking place on
> server B (and they are linked by FRS), FRS can see the
> defragged file as being *newer* than the newly changed
> file -- overwriting the new data on server A with old data
> on server B. THIS IS A REAL PROBLEM, and because FRS can
> be seriously slow when swamped with a lot of replication
> (such as false replication triggered by a defrag)
> the "window of opportunity" can be several hours wide.
>
> I can accept that FRS is a minimal utility with a limited
> set of circumstances where it is useful. But what I cannot
> accept is that this issue can lead to data loss.
>
> Loosing changes to Active Directory data sucks. Loosing
> changes to user data sucks. Fix the stinkin problem
> already. This SHOULD have been fixed back with SP-2 (or
> shortly thereafter). This is a CRITICAL issue, it should
> be handled as such through Windows Update. Even with the
> release of Windows 2003 Server, you'll be supporting
> Windows 2000 Server for the next three or four years to
> come.
>
> So how about some support. PLEASE FIX THIS!!!!
>
> Thank you.
>
> ScottyDM
>

Shobana;

Thank you very much.

The two machines in question...

SPROCKET
System:
Microsoft Windows 2000
5.00.2195
Service Pack 4
Registered to:
Scott D. Miller
The Miller Family
51877-015-1168273-xxxxx
Computer:
x86 Family 6 Model 3 Stepping 4
AT/AT COMPATABLE
458,292 KB RAM

GOBO
System:
Microsoft Windows 2000
5.00.2195
Service Pack 4
Registered to:
Scott D. Miller
The Miller Family
51876-OEM-0010222-xxxxx
Computer:
Intel(R) Pentium(R) III CPU family 1133MHz
AT/AT COMPATABLE
523,760 KB RAM

I'm also up on *all* critical updates (via Windows Update)
except for MS03-039, on both machines (I'm not running
RPCSS through the firewall so I think the patch install
and reboot can wait until morning, when things quiet
down). I'm also up on *most* relevant "Windows 2000"
patches (none missing having to do with FRS or defrag).

Is this "Q815473"?
{http://support.microsoft.com/default.aspx?scid=kb;en-
us;815473&Product=win2000} It does not seem to have
anything to do with marking handles in the defrag API. And
what is a QFE and who is PSS?

Which files are used by the defrag API and what are the
*good* file rev/build numbers. I think I can paw through
my systems, find the files, and report the actual
rev/build numbers if that would help.

Thanks again.

ScottyDM

>-----Original Message-----
>Dear ScottyDM:
>
>Yes there was a problem with with marking handles in the
defrag API on
>Windows 2000 which have since fixed in SP3. What version
of Windows 2000
>are you using? I would also recommend that you get the
latest FRS QFE for
>Windows 2000 SP3 Q815473 which has several fixes and
enhancements. You can
>call PSS and obtain it.
>
>Please post again if this issue has not been resolved
with a more recent
>service pack.
>
>Thanks,
>Shobana
>
<<-snipped->>