Embedded Open File Manager

Preparation: Setup your PeerSync Job with your Source/Target Folder and basic settings.

1. Change the drop-down list in the top left from Basic to Advanced.

2. Select the Managed Files option (or EOFM option for version 7.3 and below) from the menu tree.

3. Check the Enable Managed Files option (or Enable Embedded Open File Manger (EOFM)  for versions 7.3 and below).

4. Now click on Global Settings on the bottom of the pane.

5. Change the value of Run Managed Files List Manager every X minutes (Run Embedded Open File Manager for versions 7.3 and below) to specify how often the Embedded Open File Manager will copy open and locked files. The minimum time is every 30 minutes.

6. Save the Profile and run synchronization.

Understanding Embedded Open File Manager behavior during Scan at Start

When a Profile has the Scan Job once at Start option checked in the Automation window, the Embedded Open File Manager (EOFM) will process the files that are in-use at the end of the full scan. During the scan, the log may get messages such as:

“Could not open Source File (Added to Managed Files List)”

“Could not open Source File (Added to EOFM Locked List)” (for versions 7.3 and below)

This is not an error. This message means that the file could not be copied using the standard copy method, and instead will wait for the EOFM to run in order to be replicated to the destination. When the EOFM runs at the conclusion of the Scan Job once at Start event, the log should then reflect that these files have in fact been processed: “Managed Files initialized C Drive successfully”  (or “EOFM initialized C Drive successfully” for versions 7.3 and below)

Understanding Embedded Open File Manager behavior in Scheduled Modes

The Embedded Open File Manager (EOFM) runs on an interval independent of Job schedules, as defined in the File Options -> Open Files –> Global Settings window.

This means that at the end of a scan, messages may appear in the log file stating:

“Could not open source file (Added to Managed Files List)”

“Could not open source file (Added to EOFM Locked List)” (for versions 7.3 and below)

This is not an error. This message means that the file could not be copied using the standard copy method during the scheduled scan, and instead will wait for the EOFM to run at its defined interval in order to be replicated to the destination. When the EOFM runs, the log should then reflect that these files have in fact been processed:

“Managed Files initialized C Drive successfully”

“EOFM initialized C Drive successfully” (for versions 7.3 and below)

Understanding Embedded Open File Manager behavior in Real-Time Mode

The Embedded Open File Manager (EOFM) runs on an interval independent of Real-Time activity. If a Real-Time event is detected, PeerSync will attempt to copy the file immediately using the standard copy method. If this fails because the Source File is locked for an extended period of time, it will add it to the locked list to be processed by the EOFM. The following message will appear:

This is not an error. This message means that the file could not be copied using the standard copy method, and instead will wait for the EOFM to run at the specified interval in order to be replicated to the destination. When the EOFM runs, the log should then reflect that these files have in fact been processed:

Product(s): PeerSync

Version(s): All Versions