Syncovery Support Forum

It turns out that "Never allow two profiles to share the same database" was already checked in the program settings.

I'm taking your advice and switching all relevant profiles to "Verify copied files"

Thanks

Here are the scan results going back to Jun:

C:\ProgramData\Syncovery\Logs\DG1S3 Family Pictures - 2025-08-23 14.28.59 - 1 copied (369.6MB), Duration 02.27.12, Binary Comparisons. 1183.log 1,907 KB LOG File 2025-08-23 16:56:21 2025-08-23 14:28:59 2025-08-24 12:48:30 1
45 Using reference database in ...

I scanned my previous log files. It appears that the database has been empty since July 19. I let almost all of the profiles run to completion so I don't understand why the database isn't getting updated. I've attached several log files from when the database was last updated and several after when ...

Please review the log file for this profile to see if there is anything I can do to speed it up. When I watch the profile run it seems like if checks some of the checksums and does a full comparison on other files. I realize that there are a lot of files, some of which are quite large

tobias, thank you for another prompt and accurate fix and a useful explanation of S3 date handling. The profile ran successfully with "Nothing to do"

I back up all my photos to S3. I wasn't able to run my profile for over a month. When I did yesterday it wanted to backup all the files again. As far as I can tell S3 changed the date on all of them. I believe the contents remained the same otherwise. I've attached before and after log files. Any ...

I had the same problem. Editing the affected profiles, entering exact mirror config, confirming Overwrite newer files - Replace With Files From Source Side was checked and clicking OK fixed the problem.

Your change to SecureBlackBox SSL/TLS fixed the problem. Thanks Tobias

See attachment