-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Add an option to restic backup to override the snapshot's "paths" field #2714
Comments
We are looking for the same feature! Currently at CERN we are backing up around 170M files everyday with restic. The problem is that sometimes we are traversing a quite big folders just for a few changes that we can get quickly from namespace information prior to the backup. This is causing a lot of activity on our instances and affects user experience. Would be nice to pass directly these files to restic but linked to the main path of the backup. Something like And @asayers, is not just a visual thing, because if you restore that snapshot you will only get the files specified in the file, not the incremental view of the path. The same for the fuse view. |
I would add that it also seems to interfere with restic selecting a parent snapshot at backup as the paths field differs for each snapshot (if you have any new/deleted files). In fact this has been filed as a bug already: #2246 so a solution here could fix two bugs at once. Perhaps instead of allowing the user to set the paths field restic could set the field to the smallest unique path(s) from all the files that have been added to the snapshot? i.e if the snapshot contains:
It would set paths to |
Thanks for the suggestions. Marking as feature enhancement for now. There's lots of other issues to look at currently. |
@chrahunt reported in #2993 a few further issues caused by the large number of paths:
|
In #3200 I propose a new option |
@aawsome Great, that's exactly what I was looking for! |
This is a resurrection of the deleted aawsome:backup-set-path branch from closed PR#3200 by Alex Weiss. See also Issues restic#3198,restic#2993,restic#2714... restic#3200 restic#3198
#1376 is a duplicate of this I am running into this issue too, I am importing snapshots from another system into Restic, and I can't do that at the original path (which contains current data). |
+1 |
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?
Add an option to
restic backup
to override the snapshot's "paths" field.What are you trying to do?
My first-time restic experience went like this:
restic backup --files-from
lets me just tell it exactly which files to backup. Great!restic snapshots
, and OOOH sweet jesus!As you can probably guess, I had created a snapshot with 140k items in its
paths
field 😬. As far as I can tell, this is not actually causing any real problems. I'd just like to be able to override the "path" field when I make a backup, so that the output ofrestic snapshots
is more usable.Did restic help you today? Did it make you happy in any way?
Restic seems really good. I'm a long-time bup user, and bup is great too - but I wanted encryption so I could use a cloud storage provider. Restic seems to follow mostly the same design principles as bup, so I thought I'd give it a try. I'm liking it so far!
The text was updated successfully, but these errors were encountered: