FRS retry interval

  • Thread starter Thread starter Fari
  • Start date Start date
F

Fari

It is my understanding that the retry interval of FRS is
30-60 seconds i.e. if replications of files from computer
A to computer B fails for whatever reason, FRS on computer
A will retry the replicating every 30-60 seconds.

A couple of questions:
- Is my understanding correct?
- If so, is the retry interval configurable?

The consequence of having small interval is that ntfrs.jdb
can grow big fairly quickly if there is a lot of files
being changed when there also happens to be network
distruption that last only 1 minute or so. So, a
combination of large number of files modified and short
time network distruption can cause the ntfrs.jdb file grow
too big.

I'll appreciate any info that you can provide.

thansk,

Fari
 
The retry interval you are mentioning occurs when you have sharing
violations and FRS cannot read the file to generate a staging file - it is
failing and therefore keeps trying until it succeeds. I have not found
any information that indicates it is configurable, but if someone else
knows then by all means jump in.

The best document that is available to understand and troubleshoot FRS is
the FRS Monitoring Help File found at
http://www.microsoft.com/windowsserver2003/technologies/fileandprint/file/df
s/tshootfrs.mspx. It contains detailed information on FRS, its
terminology, how it works, what the error messages mean and how to
troubleshoot FRS.

In this particular case, download ultrasound.chm and double-click on it to
open it. Under the Contents tab, expand Troubleshooting FRS, expand FRS
Troubleshooting Topics and locate Sharing Violations.

David Pharr, (e-mail address removed)

This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| Content-Class: urn:content-classes:message
| From: "Fari" <[email protected]>
| Sender: "Fari" <[email protected]>
| Subject: FRS retry interval
| Date: Mon, 24 Nov 2003 09:44:56 -0800
| Lines: 22
| Message-ID: <[email protected]>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="iso-8859-1"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Thread-Index: AcOysqyo+R5jLx14StazTIJFn+NROw==
| X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
| Newsgroups: microsoft.public.win2000.active_directory
| Path: cpmsftngxa07.phx.gbl
| Xref: cpmsftngxa07.phx.gbl microsoft.public.win2000.active_directory:56953
| NNTP-Posting-Host: tk2msftngxa08.phx.gbl 10.40.1.160
| X-Tomcat-NG: microsoft.public.win2000.active_directory
|
| It is my understanding that the retry interval of FRS is
| 30-60 seconds i.e. if replications of files from computer
| A to computer B fails for whatever reason, FRS on computer
| A will retry the replicating every 30-60 seconds.
|
| A couple of questions:
| - Is my understanding correct?
| - If so, is the retry interval configurable?
|
| The consequence of having small interval is that ntfrs.jdb
| can grow big fairly quickly if there is a lot of files
| being changed when there also happens to be network
| distruption that last only 1 minute or so. So, a
| combination of large number of files modified and short
| time network distruption can cause the ntfrs.jdb file grow
| too big.
|
| I'll appreciate any info that you can provide.
|
| thansk,
|
| Fari
|
 
Back
Top