New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error in prune command #4689
Comments
You're using an ancient restic version. Please upgrade to a recent version of restic and try running prune again.
If the huge list of |
I have installed restic with apt. How do you think I should install it? Today I tried to run a new incremental backup and a new forget, after a prune command, the output is similar.
He don't see errors in the repo 🤔 |
Using a package manager to install your software is fine, but you have to be able to understand and identify when the package manager has very outdated versions of the software in the packages. Restic 0.9.6 was released 2019-11-22 and the current version right now is 0.16.4. Either update your Debian to a newer version that has newer packages in its APT repositories, or use backports, or you can simply download and use the official restic releases that you find here on GitHub. They consist of one single binary, so you can place them wherever you want and run them without having to do any additional installation or configuration. |
Ok thankyou, I proceed to update my installation! EDIT: I have updated to the latest restic. I have 2 doubts:
It ok? Or I need to migrate something?
🤔 I don't know if now it's all resolved |
What does The The prune output looks fine. You can verify the entire repository including all the stored data by running the |
now the vesion is:
|
That's a good version. So did you run the |
If |
Today I upgraded my repo to version 2 with the command in the docs and checked the data:
I see some errors, but probably it is a bucket fault. It is not an AWS bucket and does not have good performance. |
Yes, those errors are caused by the S3 storage and must be fixed there; there's nothing that can be done about that in restic. At the rate of errors thrown by that storage, it looks like its redundancy mechanisms are already overtaxed and it's just one minor problem away from actually losing data. |
Thank you guys for your help <3 |
Here you can see the log.
My snapshots are still safe? Or I need to do a new full backup?
In the attachments the full log
full.log
The text was updated successfully, but these errors were encountered: