Syncovery Support Forum

Concerning the timestamps, as I mentioned, S3 cannot preserve your original modification dates.

Syncovery offers to encode the timestamp into the filename, but then the names look a bit strange if you look directly at the S3 storage. It's fine for most use cases, but in your profile, you didn't ...

The problem has been fixed in version 11.5.1.

In addition, you should remove a setting in your profile that causes unnecessary delays and doesn't work with S3:

Under "Verification", remove the checkmark "Right Side". This is only for the Syncovery Remote Service, which isn't on S3.

Hello,
S3 can't actually preserve the original modification timestamps, so it's normal that you see different modification dates.

But I now discovered a bug in Syncovery 11.5.0, which causes it to believe the files' content hashes don't match.

I will release a fixed version ASAP (this weekend).

Yes it is always done.

Hello,
each uploaded file or block is verified with an MD5 checksums that Syncovery calculates locally, and Azure calculates on their side. If there is an MD5 mismatch, Syncovery will raise an exception and re-upload the file until it matches, or if the number of retries is exceeded, it will error ...

Recovery records are not necessary or useful when uploading to Azure. Corruption does not happen on Azure, or if it does, files are gone completely and not partially.

There could be hacks to invoke WinRAR but I do not believe it will be useful. You could possibly use two Syncovery jobs, one to make ...

Hello,
in the meantime, the latest Syncovery has a feature on the SMB dialog where you can choose to let it mount SMB shares rather than using the smbclientlib. Mounted shares have a few advantages, such as the ability for multithreading and no issues with percent signs.

So eine Funktion gibt es in Syncovery nicht. Dateien aus einem Ordner "Test2" werden am Ziel immer nur in denselben Ordner kopiert, niemals in einen anderen wie "Test3". Das Überschreiben neuerer Dateien ist hier nicht das Problem. Syncovery würde das niemals so machen, egal ob neuer oder älter ...

Hello,
in the last screenshot, you did not place the checkmark:

X Unattended File Deletion Allowed

In addition, please note that the limits of 20% and 1000 can also cause deletions to be disabled if there are too many files to delete. That means if you make an artificial test with only 20 files ...

Hello,
yes, to use the Recycle Bin, you would choose "Delete Permanently" on the SmartTracking dialog.

And then in the "Files" settings category, on the tab sheet "Deletions", you can enable the Recycle Bin (in fact it should be enabled by default for deleted files).