Syncovery Support Forum

Hi, also die Run Time Library, die Syncovery verwendet, holt die Zeitzoneninfos aus /etc/timezone oder /etc/localtime oder /usr/lib/zoneinfo/localtime Der Profil-Editor verwendet allerdings JavaScript mit der lokalen Zeitzone des Browsers. Daher können sich Zeitangaben unterschiedlicher Zeitzonen ve...

Oui, prochainement!! Prochaine semaine.

Hello,
thanks for your request, yes this seems possible to add. Do you need it to match Windows 10 Dark Mode, or just generally dark?

Yes, eventually this will be made possible. For now there are a few more pressing areas to work on.

Hello,
profiles are sorted alphanumerically. In addition, they are grouped by the first word in the name.

So if you have multiple profiles named
Backup Office
Backup Database
Backup Work
Sync Office
Sync Databsae
Sync Work

then you will get two groups named Backup and Sync.

I have been in contact with the original poster thru our support email address. Apparently the listing via SFTP just doesn't work with this server. In that case, there are two possible solutions: You can use "Cache Destination File List" or the archive flag filters to avoid re-copying files. The cac...

Version 9.01 is now available, and it uses a better method to set timestamps and attributes. Apparently this fixes the issue with IceDrive.

By default, Syncovery copies only new or changed files. If it re-copies files, then something is wrong and we need to find the cause. Possible causes include: a) the timestamps of the uploaded files are incorrect. Either there is a timezone offset which needs to be fixed, or the server does not allo...

With Robocopy, the timestamps are fine. Syncovery won't set any timestamps at all, if robocopy is set as an external copying tool. Maybe you didn't set the following option to 0: Use only for files larger than X Bytes. With robocopy, you need to use the following command line in the External Copying...

OK apparently there was some delay ... now I see them, with correct timestamp, copied by Syncovery. But when I copy with XCOPY, at first the timestamp is correct, and then after a refresh, it's set to the current timestamp. So the problem is not Syncovery specific at all. It's an IceDrive bug. Never...