| Author |
Message |
Rob
Guest
|
Posted:
Thu Jul 21, 2005 4:52 pm Post subject:
excessive local changes |
|
|
A significant number of changes have occurred on this member. This could be
a sign of excessive replication, high CPU, or high disk usage by the ntfrs
service.
i am getting this error in ultrasound on 3 of my 6 servers. i have disable
the antivirus app, theres no event log being generated, i have stoped and
started both the ntfrs and dfs service. i cant seem to figure out what is
causing this excessive local changes.
thanks
--
Rob
MCP |
|
| Back to top |
|
 |
Rob
Guest
|
Posted:
Thu Jul 28, 2005 4:52 pm Post subject:
Re: excessive local changes |
|
|
Does anyone have an idea on this please?
--
Rob
MCP
"Rob" <rfretz@mscu.com> wrote in message
news:hq6dnTtk5a32LULfRVn-og@golden.net...
| Quote: | A significant number of changes have occurred on this member. This could
be
a sign of excessive replication, high CPU, or high disk usage by the ntfrs
service.
i am getting this error in ultrasound on 3 of my 6 servers. i have disable
the antivirus app, theres no event log being generated, i have stoped and
started both the ntfrs and dfs service. i cant seem to figure out what is
causing this excessive local changes.
thanks
--
Rob
MCP
|
|
|
| Back to top |
|
 |
Richard Chinn [MSFT]
Guest
|
Posted:
Sat Jul 30, 2005 8:06 am Post subject:
Re: excessive local changes |
|
|
Regarding the excessive local changes alert, was your replica working
okay before (no excessive local changes), or did you start seeing
problems immediately after installing Ultrasound (i.e. you have no
baseline)? If it was working before and this new alert started
popping up, you're right to suspect certain applications like
anti-virus. Other applications might include backup software or any
new user applications that update files rapidly without making changes
to the data.
To see if you're really having problems or not, be sure to drop
propagation test files to verify replication is working well. If it
looks like replication is fine, you can rest a little but should try
to identify the application(s) that are making changes to files. You
might be able to use filemon.exe from sysinternals.com to catch
suspicious activity, but if the server is normally busy, there will be
a lot of noise to sort through.
--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 Thu, 28 Jul 2005 09:03:59 -0400, "Rob" <rfretz@mscu.com> wrote:
>Does anyone have an idea on this please? |
|
| Back to top |
|
 |
|
|
|
|