Backed up too much

Getting Help
1

I am using restic through autorestic and using the backblaze s3 endpoint.

I accidentally backed up a folder with a large amount of files I did not intend to. (Typo in exlclude).
Locally I managed to exclude the folder with the rewrite command but the remote is still the same size.
Is there a command to update the remote with the local snapshots?

2

When creating a new post in the Getting Started category, you are asked for some relevant information such as what actual commands you ran, and some other things. It appears that you actively chose not to provide this information, which makes it hard to give you a useful answer.

Please see the documentation at Working with repositories — restic 0.18.0 documentation , in particular the mentions of “forget” and “prune”. I’m guessing that might help. If it doesn’t, you probably have some retention in your S3 bucket that makes the data take up space despite being deleted by restic.

1 Like
3

Thanks for the hint. You assumed correctly that I forgot to configure the backblaze Lifecycle Rules.

This is documented here: https://restic.readthedocs.io/en/stable/030_preparing_a_new_repo.html#backblaze-b2

I overlooked it because I directly switched to the s3 compatible section as this is the recommended way of using backblaze.

Now I just need to wait until the new policy kicks in.

4

Or… You could click the link @rawtaz provided which directly answers your question, nothing to do with remote storage policies.

5

I think following command would remove the snapshot from local (also from remote), need --prune explictly because it is not automatically remove old data.

restic forget <snapshot id> --prune

–
Edit: correct typo.

6

48h after correctly setting the policy in backblaze the size was the same as locally.

2 Likes
7

I think you mean “prune” rather than purge. It’s restic forget --prune <snapshot id> :slight_smile:

8

Yes, thanks for correction the typo. :sweat_smile:

1 Like