Syncovery Support Forum

Files in the directory are :

2007-05-20 15:20:02.000000000 +0200 main~1.HEX
2007-05-20 15:20:02.000000000 +0200 main.BAK
2007-05-20 15:20:02.000000000 +0200 main.c
2007-05-20 15:20:02.000000000 +0200 main.cof
2007-05-20 15:20:02.000000000 +0200 main.err
2007-05-20 15:20:02.000000000 +0200 main.HEX ...

Thank you tobias for the 10.15.10 release.

I managed to not send my data all over again thank you.
I disabled "Overwrite newer files" under "Exact mirror" settings.
And I had to enable"Double-check the actual destination for those folders where new or updated files seem to exist" in "Destination ...

sorry if this doesn't work for you as it is now. Maybe I can implement a solution relatively quickly, if you can wait for a few days?

Ho that would be great !! Of course I can wait.

....Therefore the synchronization needs to be done based on timestamp only. Which might be good enough actually ...

Thank you Tobias for the quick answer ! :D

Unfortunately my use case is to get an exact mirror involving 365 days delayed deletion on target (as per the ZIP-compression-encryption functionality).

I thought it was great to switch to pgp but I should have tried before sending 500Gb over to GCS ...

When using "Cache destination File List" and ZIP compression with password encryption all is working as excepted.
- On first profile run, all files are copied (for example left to right on Google Cloud Storage)
- On next profile run, only the modified/moved/deleted files are processed.

But when ...