Windows Server

Chandru R · Guest

Hello All,

I have a few general FRS questions. I have 1 DFS root setup with 1 link (3
servers) - which use a full mesh topology.

1. For certain directories / files created by an application I need to
ensure that the files written to one are propagated out real time to all 3
servers. I think there is a delay due to the aging cache policy (3 seconds).
Is this modifiable? Is FRS the right solution for such aggressive file
replications? Are there any alternative products?

2. I could have the application write out to all 3 servers but it renames
the files with _NTFRS_xxxxx prefix and replicates them back out to all the
servers generating a lot of junk. Is there a way to override this default
behavior and simply merge all the folders. Are there any other cons of this
method (any conflicts between FRS and the application writing out).

Essentially I need the files to be available on all 3 servers if the server
is online and if a server is not - I was hoping I could use DFS / FRS to
help keep the server(s) in sync when they come backup.

Any advice would be appreciated.

Thanks
Chandru

Glenn L · Guest

inline.............

--
Glenn L

CCNA, MCSE (2000,2003) + Security
"Chandru R" <chandru2@hotmail.com> wrote in message
news:usw7whbzEHA.2572@tk2msftngp13.phx.gbl...

Richard Chinn [MSFT] · Guest

FRS is generally not suitable for "aggressive" file replication. In
your scenario, you need to be very careful of file and folder
conflicts. They are resolved differently. In the case of file
conflicts, FRS determines a last writer and that writer has its
content win. This means other versions of the file will be lost.

For folders, FRS will perform a "name morph" by adding on the
"_NTFRS_xxxxxxxx" suffix to the folder name. Both folders are
retained, the winner keeps the real folder name and the loser gets the
suffix. Morphs are difficult to clean up and if done improperly may
lead to additional morphs.

Since FRS is a multimaster replication system, there is no simple way
to "merge" the results. There is no feature in FRS to support this
nor is there a way to configure it to perform merges. Merging is left
to the administrator, so it is best to make an attempt to ensure
morphs do not happen in the first place.

I suggest taking a look at the FRS Monitoring Help File. At the
beginning are a few pages of information about appropriate and
inappropriate uses for FRS. The help file comes with Ultrasound, or
you can download it separately. Go to http://www.microsoft.com/frs.
Follow the link for "FRS Troubleshooting and Monitoring." Then save
the "FRS Monitoring Help File" link to your local machine to view it.

There is a lot of other background information available on FRS at
http://www.microsoft.com/frs that you may find useful.

--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, 18 Nov 2004 16:49:10 -0500, "Chandru R" <chandru2@hotmail.com>
wrote:

	Windows Server Forum Index -> DFS and FRS	All times are GMT
Page 1 of 1