backup --files-from includi.txt --exclude-file=windows.escludi --exclude-file=custom.escludi --verbose=2 --limit-upload 1000
when add a new path to includi.txt , backup no found parent snapshot, can i use --group-by=host
i want only host, not --group-by=host,path?
i have only one server windows, with many folders.
Does your include.txt file have a path on each line and without commas or anything separating it?
Also check this link:
Sorry for misleading you about your --files-from option. Of course this is equal to just putting all paths to the command line.
In your case the problem is that
resolves the paths to all entries within this dirs. So if files or dirs within those two dirs change, you have changed backup paths and restic will not find parent snapshots.
instead. (The same could be achieved using the PR above, but you are right t…
Maybe you are including a path that is part of another previous path.
And this is a question for me, what kind of content do you have in windows.escludi? Temporary files, program folders, etc?
restic.exe backup --files-from includi.txt --exclude-file=windows.escludi --exclude-file=custom.escludi --verbose=2 --limit-upload 1365
after i add c:\tmp2
no parent snapshot found, will read all files
load index files
start scan on [C:\\tmp c:\\temp c:\\tmp2]
start backup on [C:\\tmp c:\\temp c:\\tmp2]
# default excludes
# examples https://github.com/duplicati/duplicati/blob/master/Duplicati/Library/Utility/FilterGroups.cs
C:\Documents and Settings
C:\System Volume Information
C:\Program Files (x86)
# cloud services
# misc. temporary files
Temporary Internet Files
custom.escludi is empty
So I’m very sorry but I have no way to help you. I’m pretty new to Restic.
Thank you very much for sharing the exclusions file!
I believe this is down to restic’s design - a key part of how it finds a parent snapshot is by using the paths that were passed to backup (
Backing up — restic 0.16.0 documentation). The relevant quote from the docs is: “By default restic groups snapshots by hostname and backup paths”.
You are adding another path to backup (c:\tmp2), which means restic cannot find a parent automatically, hence the “no parent snapshot found” line.
Manually specifying a parent snapshot should help with the backup speed, as discussed here: (
Backing up multiple paths at once).
The docs mention you can set grouping by tags, host, and not paths, which might work to enable the parent to be automatically detected. I think it’s worth trying (maybe while using --dry-run) to see what the effect of grouping by host is, and if the parent snapshot is detected properly.
solved i used 0.15! on 0.16 backup have --group-by !
--parent snapshot use this parent snapshot (default: latest snapshot in the group determined by --group-by and not newer than the timestamp determined by --time)
Great! Happy that you find the solution and also the info.