Check integrity of ZIP backups after system error?

[Hayframe]

Hello,

I am making three backups of my files on three different local drives.

I've recently gotten a complete system error while performing a backup to one of the three drives.
The backup type is an exact mirror with ZIP compression.

After reboot, I've run the backup job again so that it completes the backup on that drive.

Later, I've manually checked some of the latest files in the drive I was making backups into. Some of them were unopenable ZIP files. I've checked the same file on the two other drives, and I could open them.

I've run the profile on that drive, and it did not find any files to update.
Therefore I deleted that file, and I've run the profile again. I was able to open that newly generated backup.

I believe Syncovery was confused and had no way to compare the ZIP file with the real file to figure out it was in a corrupt state (same timestamp, same uncompressed size).

In the end I've decided that my backup was compromised so I've deleted the backup to build it back from scratch.

Is there an option somewhere:

[*] To ensure that while making the backups, if the system errors out in the middle of writing a file, Syncovery will recognize these ZIP files / the latest backup state are in a corrupt state?

[*] To run an integrity check of the backups without needing to create a profile with the Binary Comparaison of Existing Files?

Thanks.

[superflexible]

If you use "Zip Directly To Destination" from the Zipping tab sheet, or "Automatically Resume" from the Files tab sheet, then the zip file will be created with a temporary filename and only renamed when complete. This excludes the possibility of corrupt files.

You can right-click a job and choose "Test Backup Integrity", which downloads each file to the TEMP folder and deletes it immediately once verified.