Files dissapear if user shutdowns during sync

[ukcarl]

Hello,

We have Superflexible setup so that our users run a two way sync, every hour between their local hard drive and a WebDav folder.

Users have reported that occasionally files on their local drive go missing. This seems to be new or recently mofdified files located on their local hard drive. Once the usual runs a full sync again these files reappear.

After some troubleshooting I think this happens when a user shuts down their laptop while a sync is running. Is this expected behaviour? If a user shuts down the PC and therefore forces the SuperFlexible sync to end halfway through I wouldn't expect files to be missing just that the sync would not be compete.

Thanks

Carl

[superflexible]

I haven't heard of this problem yet but please make sure you are using the latest version 5.10. Theoretically if a transfer is interrupted in the middle of a file, that one file might go missing. The way to avoid that is to use the "Auto-Resume" checkmark. This feature will use a temporary filename during transmission and only replace the original file when the transfer is complete. You will find the option on the Files tab sheet.

If problems remain, the issue can be analyzed by looking at the log files. You might want to turn on the SmartTracking details on the Logs tab sheet of the Program Settings dialog. Also check that it will keep a sufficient number of log files per profile, such as 50. Then if the issue comes up again, you can let me know which file is missing and send me the log files to support@superflexible.com and I can analyze exactly what went wrong.

Cheers,
Tobias Giesen

[superflexible]

One thing I just found out is that the following SmartTracking setting is not compatible with WebDAV or other Internet Protocols:

Conflicting Files-> Rename On One Side & Synchronize Both Versions

This has not been implemented for WebDAV, FTP etc. The next version will issue a warning and turn the option off automatically.

[ukcarl]

I'll try using the Auto-Resume checkmark and see if this makes a difference.

It's still also hard to recreate the problem all the time so I'll monitor our users and see if there is anything useful in the log files next time it happens.

Thanks

Carl