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
Cache is newer than repository, refusing to continue #123
Comments
In an attempt to fix this, I removed the .cache folder located in my home directory. I am hoping this was a safe move. |
This check is in place to detect when a repository has been replaced with an older copy of itself. This happens naturally is situations like when the repository itself is restored from backups. But it could also mean that an adversary is trying something. Anyway, removing the cache folder is always safe but might be a bit time consuming to rebuild. |
Things that might improve the user experience:
Maybe add an "attic cache" command with various options to do things like refresh / overwrite / force-update a specific UUID. To fix the option in my case I had to:
So maybe being able to type the following would be easier:
Note sure if "--reset" is best wording choice. Alternate options might be "--wipe" or "--delete". |
I am doing some tests with "borg recreate" and, as it is an experimental feature, before doing so I copied the repository with another name before that. Now I want to use the original repository renaming it to its original name and I get the message: Yes, they are newer than the repository, for sure. Is there any way I could use the old repository? Removing the cache of that repository did not help. |
I am running into an error with my repository when I attempt to run a prune command.
attic prune attic-backup@myserver:mybackup-42977.attic -H 0 -d 7 -w 4 -m 12 -y 0 -v
"attic: Error: Cache is newer than repository, refusing to continue"
However, I am stuck. How do I clear up the cache, or more generically, how do I resolve this error?
Running: Attic 0.13 - Deduplicated Backups
The text was updated successfully, but these errors were encountered: