Backup corrupted

Oct 8 fix will presumably be out in the next Canary after current v2.0.9.108_canary_2024-10-03. Canary releases by definition are new and untested, so beware of bugs. Testing help does help.

Tracking down your annual issue if it’s on 2.0.6.3 might just find it’s fixed since, but working with something more current may be useful. It may involve lots of attempts to preserve historical info.

Ideally what one wants is probably a GitHub Issue with exact steps for anyone to repro a failure. Actually a pull request would be better, but heading the other way, one collects data for the devs.

Suggestions from me are available, and I collect a lot, and try to avoid a latent-problem situation. Sometimes this means test scripting to do a more intensive check than you (or Duplicati) now do.