Keyword search: 

Realtime Replication Buffer Size Issues in Windows

5/5/2008 5:31 AM
You can subscribe to this wiki article using an RSS feed reader.

Problem:

Real time replication stops working after I try to replicate a large number of files.

The logs display an error message:
"Failed to read real-time directory changes from Windows".




Solution:


When large quantities of files are copied, changed, moved, or deleted at the same time, a large number of events are generated which may cause buffer overruns. In such cases, you will be notified by the following error message:"Failed to read real-time directory changes from Windows".
If this occurs, please follow next instruction to set FRP events buffer size to a larger value.

FRP system parameters configuration file (named "s2s.properties" located in the /FileReplicationPro/libs directory) has two parameters that control real-time events buffer size:

(1) s2s.realtime.events_buffer_size
(2) s2s.realtime.network_drives_event_buffer_size

s2s.realtime.events_buffer_size:
================================
This parameter determines a buffer size (in Kb) use to hold events related to WINDOWS LOCAL DRIVES.
The default value for s2s.realtime.events_buffer_size is 1024 (which means 1MB).
This value can be adjusted depending on the number of real-time events that occur on the system.

s2s.realtime.network_drives_event_buffer_size:
==============================================
This parameter determines a buffer size (in Kb) use to hold events related to WINDOWS NETWORK DRIVES and SHARES.
The default value for s2s.realtime.network_drive_events_buffer_size is 64 (which means 64KB).
When setting the s2s.realtime_events_buffer_size value, please consider the following limitations:

Windows 2000 (with no service pack 2 or higher) - maximum value for s2s.realtime.events_buffer_size is 64.
Windows NT 4.0 - maximum value for s2s.realtime.events_buffer_size is 4.


-Stephen 05/05/08
Tags:
Home: WIKI - Knowledge Base Index What's new: Recently changed articles