1. What does the code "SPCSX" in Last Result mean?
2. Sometimes when using ExtremeSync Remote Service, if we altered the values of "Maximum listings to process in parallel" and "Maximum checksum requests to process in parallel", or added some folders to watch, then clicking "Apply", the program just hanged and was not responding. In Windows Services Manager, we saw that the status of ExtremeSync Remote Service was "Pausing" and couldn't do anything about it. Only if we opened Task Manager to manually kill "ExtremeSyncRemoteService.exe" process, then we can restart the program. what's wrong?
3. Following 2, When the local site is running a profile which status is "Waiting for remote listing (XXXs)", and if on the remote site the ExtremeSync Remote Service hangs and is killed then restarts, the local site will wait indefinitely. We must restart the SFFS service on the local site, then it can start to do sync jobs. Why is that?
4. What is the recommended values of "Maximum listings to process in parallel" and "Maximum checksum requests to process in parallel"? Our spec is 2 2.4Ghz CPUs and 4GB RAMs.
5. In the profile, there is a setting in "Files" tab: "Number of files to copy in parallel". Does this mean that we can open such many threads to simultaneously copy files? However, we had limited that one download/upload thread can only process about 2~4Mb/sec and set the parallel file processing number to be 10; so during copying, the network flow should have been 20~40Mb/sec. But the network flow was still 2~4Mb/sec. What exactly is the mechanism of parallel file copying?
6. What is "No full copying if service unavailable" under "Use Partial File Updating" in Special tab?
7. When remote site is unconnected, the local site running SFFS will show "Waiting for Availability". But after the remote site is back online, it still showed "Waiting for availability" and will not start to sync files. Why?
8. I really hope you can release the explanations of processing codes under the "Last Result" area some day.
Sorry to constantly bother you. Thank you so much.