I have Duplicacy set up to create a local backup of my system, which is then copied to Backblaze every 12 hours. On Sunday, I run a prune on both, followed several hours later by a check on both.
Last Sunday, both prune operations ran fine with no errors. The following local check ran fine with no errors. The Backblaze check, however, reported a missing chunk for revision 27624. I found a log entry that said chunk was previously copied to Backblaze, but no logs report it being deleted.
I looked for the chunk in the local backup. Revision 27624 is still listed in the restore options for the local backup, but that chunk does not exist. However, I found no log errors that the chunk is missing from the local backup.
I ran both prune operations again. The Backblaze prune now reports the same missing chunk.
I deleted .duplicacy-web\repositories\localhost\all.duplicacy\cache. I then ran the Backblaze check again. Now I get errors for 871 chunks missing from multiple revisions across different snapshots.
All of the revisions related to those missing chunks are not listed in the restore options for the local backup. (Revision 27624 mentioned above is now gone, as well.)
I checked for some of those revision numbers in the previous Backblaze prune log and they are logged as being deleted. But, they are all still listed in the restore options for the Backblaze copy.
I’ve been looking through logs so long now, I can’t think straight. Before I mess something up out of frustration, what should be my next step?