Backup pruning fails on specific revision

[gingab]

Hello, I am trying to prune some revisions but duplicacy fails on “fossilizing” a random chunk of a specific revision (210) of my backup.

Revision 210 is the one where I (erroneously) pushed a significant bulk of unwanted data, which is why I am now trying to delete it.

Any idea on how to fix this? Is the data integrity of my backup now compromised?

.\duplicacy_win_x64_2.2.3.exe prune -r 81-210
[…]
Deleting snapshot at revision 210
Failed to fossilize the chunk 8fcbde7a91ce4c153a3f26869271b3e940606bd79486ed4911c8bb293b7e902f: URL request ‘https://api002.backblazeb2.com/b2api/v1/b2_hide_file’ returned 401

.\duplicacy_win_x64_2.2.3.exe prune -r 81-210
[…]
Deleting snapshot at revision 210
Failed to fossilize the chunk 3fa0674f637457057669ad13b52e700a3f7edbfdb21c16ce63164d6db6e4a929: URL request ‘https://api002.backblazeb2.com/b2api/v1/b2_hide_file’ returned 401

Thanks!
Gabriele

[towerbr]

You are using version 2.2.3. First of all I suggest upgrading to version 2.3.0, which has an increased number of retries for B2 backend.

Although error 401 is related to authorization:

B2: Auth error (401)

On and after about 6:00 today UTC, duplicacy (duplicacy_linux_x64_2.2.2) caused authorization error (401) when executing list sub-command to B2 cloud storage. The error message is as follows: [0] URL request ‘POST https://api002.backblazeb2.com/b2api/v1/b2_list_buckets’ returned 401 I tried using older version (2.1.2) but not succeeded. And other Linux machine causes the same error, too. Then I have read B2 API doc. and noticed that it describes about API v2 but duplicacy uses v1 like (shorte…

[gchen]

Could it be that the application
key you’re using doesn’t have the writeFiles capability so it can’t make changes to the bucket: Application Keys?

[gingab]

That was exactly the problem. Seem quite obvious now but I had completely forgot the key was setup as read-only for testing purposes.

As a possible enhancement it might be worth adding some more textual description of the error(s) as opposed to the HTTP Status Code (“401 Unauthorized Error” as towerbr pointed out)

In any case, thanks for your help!
Gabriele