Keyword search: 

Real Time Alternative Setting

2/10/2012 5:25 AM
You can subscribe to this wiki article using an RSS feed reader.

For some operating systems and devices that do not support real time in File Replication Pro there is an alternative job setting that can give virtual real time performance at a small cost in resources from the CPU and Memory.

Examples of these OSes are Netware, AIX, SUN, and NAS or SAN devices.  A NAS or SAN is unable to have the FRP replication module installed and running in it's OS so real time detection, compression, bit level replication and encryption are not possible with these devices.  Also since the FRP protocol for file transfer is absent on the NAS or SAN, file transfer speed will not be optimized.

These settings will put FRP into a mode of continuous change detection1 rather than using an OS level hook to receive reports of file events.

What is performance when using this option?

On a modern machine (2 processors and 4GB ram or better)  that is not otherwise heavily tasked with other programs, the cost to CPU and memory is hardly noticeable.  There will be more drive activity and the /FileReplicationPro/logs/txt  folder will grow and may need to be cleaned up from time to time by the administrator or using a script run in cron on systems with very small OS partitions.  The additional logging is caused by the large number of events created in this configuration.

To configure this mode, edit the following sections of the job in the GUI.

Basic Job Attributes

The job type must be set to Repeating Job

Schedule Job

The Repeat Every:  settings are set to  0 Minutes

Optionally the administrator can use other settings in the Schedule Job section to limit the times of day or days of the week when this mode of operation is in use.  IE:  If you only need virtual real time during working hours you might try settings which use and  Except from: period beginning at 7:00 PM and for a duration of 12 hours on Monday through Friday (unchecking  Sat and Sun) so that this mode will not be active during those times.  You could then create another job on the same source and destination folders which would be set only during the exclusion period you just created and that job could run on some other schedule such Repeat Every 1 Hours.

1 NOTE:  Administrators may also want to see our WIKI article on File change detection and replication methods 





Tags:
Home: WIKI - Knowledge Base Index What's new: Recently changed articles