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
restic-rewrite: change snapshot metadata #2654
Comments
@ATLief Thanks, but can you be more specific about your use case? Please give one or a couple of concreted examples of what metadata you want to change, from what and to what. |
ID Time Host Tags Paths Current:
Desired:
Current:
Desired:
Current:
Desired:
Current (Hypothetical):
Desired (Hypothetical):
All without changing the actual content of the snapshots. |
You can already add/remove tags with the As the snapshot ID is defined by the hash of all snapshot metadata, there's no way to keep the ID identical across changes or even modify it. |
I have opened a (draft) pull request which allows rewriting host and time of a snapshot. |
@gab50000 are you working on rewriting paths, as the issue asks? Because that's exactly what I just asked in the forum. If not, I would try myself. |
Output of
restic version
restic 0.9.6 compiled with go1.13.4 on linux/amd64
What should restic do differently? Which functionality do you think we should add?
restic should have the ability to change the metadata of existing snapshots. Properties that should be modifiable include: Paths, Host, ID, Time, and Tags.
What are you trying to do?
Since moving to restic, I have converted previous system backups (from different backup solutions) into restic snapshots with the appropriate metadata. Unfortunately I made a few mistakes with some of the snapshots' Times and Paths. If I'd like to correct those mistakes now, I'd need to restore each snapshot, remove it from restic, and back it up again with the correct metadata.
This also has the unfortunate side effect that when I specify
--path
, these older snapshots aren't selected for listing for forgetting.The text was updated successfully, but these errors were encountered: