Syncovery Support Forum

Veuillez noter qu'un compte de service doit être saisi dans le fichier Vault.ini. Vous ne pouvez pas copier la section chiffrée [graph_service] depuis une autre machine. Vous devez la saisir à nouveau en suivant les instructions ci-dessous (Step 5: Adding the App Details to Vault.ini):

https://www ...

This is the encoded deletion timestamp.

You can remove the checkbox ‚Remember deletion date and time‘.

But if you use the Restore Wizard to restore files, Syncovery will automatically decode the filenames.

Hello,
yes, it can sometimes be necessary to switch between the tabs to update the display. That is a fairly normal procedure in using the program.

Ideally it would not be needed, of course. Please check if a Syncovery update is available too.

Yes, you can delete them!

Concerning the encryption message, we would need to look in the log file, you could reply with No and then cancel the job and then look for lines about filename encryption in the log and/or send it to support@syncovery.com.

Hello,
yes, you can use the SmartTracking mode, which defaults to not re-copying deleted files. It uses a database.

Even better could be using checkmarks under "Filters". On Windows, you would use the two archive-flag checkmarks.

On Mac/Linux, Syncovery can mark copied files as copied and not re ...

Hi,
also mit der aktuellen Version 11.5.2 kann ich das nicht nachvollziehen. Vielleicht kommt es auch darauf an, was genau an dem Zertifikat nicht stimmt. Vielleicht unterbindet ja auch eine andere Software die Verbindung (Internet Security).

Falls das Problem bleibt, bitte Logdatei an support ...

Hello,
the best way is to use the Google Drive web interface to move the folder. Are you able to identify the source and destination folder?

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).