Hi all, I recently started using duplicacy to run my backups, and I set up two separate backups of different folders to different backblaze buckets. I set up a schedule to backup, then check, then prune all 2 hours apart. One of my backups seems to be working just fine, but one says missing chunks every time I check. When I noticed this I decided to just delete it and make a new bucket and try again. As soon as I finished my first backup and ran a check, it again said missing chunks. Anyone know what’s going on here?
I’d first check whether the failing job’s backup log says it really finished cleanly before the check starts. On a brand new bucket, missing chunks right after the first run usually points to an upload that did not complete (or something on the bucket side deleting/expiring objects), not prune. If you can, run one manual backup for that storage, then a check before the scheduled prune, and compare it with the working bucket’s storage settings/lifecycle rules.
1 Like
I just tried making a totally new bucket again and I had the same thing happen. I think my three backups are all set up exactly the same, and running check right after a first backup of this one folder returns missing chunks right away.
Would greatly appreciate any tips to figure out what’s going on
One quick update here. I checked the logs and didn’t see any errors on the backup itself. The check log is very short and just shows one chunk that can’t be found
Not witnessed it myself, but I’ve seen several reports over the years about how, after the first backup, a check job says it’s missing chunks. Once things get going, reports of missing chunks go away. But dealing with that first revision is key, because Duplicacy may keep referencing missing chunks in future jobs…
Instead of starting from scratch, what you can do is it to delete just the /snapshots folder on the storage destination, then run a new set of backups. It’ll skip uploading chunks (because they should already exist), and you’ll end up with a fresh set of snapshots that should check okay.
Make sure the initial backup and check are good before continuing.
Edit: I might add… my leading theory on this is a dirty cache. Since new users running their first backups tend to make several attempts. (So it might be a good idea to delete the local cache under .duplicacy\cache after deleting /snapshots.)
1 Like
I did both of the things you suggested, and that resolved the issue. Thank you!