Monitoring Folders... isn't ": (

[dfinlayson]

Server1: Data Origin
Platform, OS & Software being used:
Mac Pro (MacPro5,1 Quad-Core Intel Xeon 2.8GHz)
Snow Leopard Server 10.6.8
Super Flexible File Synchronizer 5.61 build 289

Server2: Data Duplicate (Mirror of Server1+"Older" versions & "Deleted")
Mac Pro (MacPro3,1 Quad-Core Intel Xeon 2x3.2GHz)
Snow Leopard Server 10.6.8
ExtremeSync Remote Service App 5.55 (all destination folders have been added to the "Configure Checksummer And Remote Lister")

SFFS Server1 Profile(s) Standard options:
Copy Left to Right, Exact Mirror
-Left hand side being the Server1 Data origin, and where SFFS is running
-Right hand side being the Server2 Data Duplicate, and where ESRS is running
Schedule
-Each profile has a nightly Schedule runtime + Monioring / Real-Time turned ON
Files
-Files -Detect Moved Files, Adjust On: Right + Detect Renamed Files turned ON
-Files -Deletions, Move Deleted Fiels Into A Specified Folder… turned ON + Delete Older Versions Permanently… ON
Safety
-Unattended Mode -Overwrite Read-Only Files + Overwrite Larger Files with Smaller… + Newer Files May Be Overwritten If Nec… + File Deletion Allowed, Max 100% Of Files From Either Side ON
-Configure… Delete Files From Destination Side If Not… + Overwrite Newer Files ON
Special
-Special Features, Right side listing uses Remote Service ON
-Database, nothing filled in apart from Database Name To Use
Versioning
-Versioning, Keep multiple backup versions "3" + Move into folder "Older" + Recreate tree below one "Older" folder ON
-More, Remove parenthesized version numbers… + Do Not Decode Left… + Do Not Decode Right… + Clean up all older versions… ON

Problem:
Although in the SFFS application window the Next Run says "Monitoring Folders" when files on Server1 get added/deleted/modified those changes are not being reflected on Server2.
I need to know how to confirm that the Remote Service running on Server2 "Data Duplicate" is creating a real-time database and that SFFS on Server1 is able to access and read it.

If I try to "nudge" a profile back into action by selecting "Run in Background" the column "Last Result" shows "Waiting for remote listing (no.of secs waited here)" and I notice "SFFS.listingrequest.$$$.xxxxxxx.$$$" appear in the destination volume which was not there before.

Sorry to bother you guys about this, I promise that once this is sorted I will leave you in peace ": )

Dave

[superflexible]

First, you need to know that the real-time monitoring feature is completely independent from the Remote Service on the destination machine. Real-time operation does not use the remote service and ignores the checkmark "Right side listing uses remote service". The Remote Service is only used for full runs such as the nightly schedule.

When the monitoring/realtime feature works, you should see that on the Schedule tab sheet. Whenever a change occurs, the word "Monitoring" should be replaced with a next run time in a few seconds, where the profile is launched in order to check what has changed in the folders. If this never happens, and all you see is "Monitoring", then something is wrong. You could try installing the latest update from our web site and rebooting the server. Note that the monitoring only runs as long as you are logged on. If you log out, the program is stopped.

However, it's possible that the storage system you are monitoring does not support real-time features. If the storage does not send any change notifications, then it simply won't work and you need to resort to full, scheduled runs. Usually, local hard disks connected directly to the server should work fine. Maybe something is configured on the server to prevent the change notifications. But I am not aware of what that would be.

Concerning the Remote Service, when you see the SFFS.listingrequest files, that is good. But the Remote Service should see them also, and it should process them. You should be able to see that in its program window. You should see "Tasks Running: 1" and then a new listing file should appear and the listingrequest file should disappear (if the app has sufficient permissions to do that in these folders).