I am getting failed message on pruning with the following settings: -keep 365:365 -keep 30:30 -keep 7:28 -keep 1:1 -a
show_log.txt (61.4 KB)
Log showing chunks already fossilised.
Check job also errors with missing chunks message.
What am I doing wrong?
From your log:
2026-01-16 01:28:20.003 ERROR SNAPSHOT_DELETE Failed to delete the snapshot PMA-Duplicacy-PMADATA at revision 22: URL request 'https://api003.backblazeb2.com/b2api/v1/b2_delete_file_version' returned 401 Access Denied
Failed to delete the snapshot PMA-Duplicacy-PMADATA at revision 22: URL request 'https://api003.backblazeb2.com/b2api/v1/b2_delete_file_version' returned 401 Access Denied
Why Backblaze returning access denied?
- Maybe the key lacks deleteFile capability (how was the key created? Can you inspect keys and confirm? If not, create a new key and ensure deleteFiles capability is present.)
- Maybe object lock is enabled on a bucket?
The failed check is result of failed prune — snapshot file is still present but chunks it refers to have been fossilized.
Backblaze key is fine for deleting but yes we do have object lock in place set to 30 days.
To confirm, check when was the file snapshots/PMA-Duplicacy-PMADATA/22 uploaded on the backblaze side. If it’s les than 30 days – then that’s the answer.
Then adjust your prune policy accordingly. Alternative solution is to avoid object lock and to use two sets of keys as described here How secure is duplicacy? - #30 by tallgrass