Do you (in your script) manually set the parent?
Nope, I set some variables and then do
$RESTIC backup --quiet --cache-dir $CACHE $BACKUP_PATH | tee -a $LOG
What was the last version of restic that worked? 0.12.1?
Correct.
Upon further inspection, I think there may be 2 (unrelated?) issues going on here.
Issue 1 - (kind of solved): Ignoring "7276c03d43178fca": no matching ID [...]
After the backup, I gather some stats about the last backup and write it to a sqlite DB (to display them on an internal website). The command I use(d) to get the id of the last snapshot was:
restic snapshots --latest 1 --json |jq -r '.[] .short_id'
With 0.12.1, that output a single id. With 0.13, this gives me 2 snapshot ids. Thing is: To verify, I re-downloaded restic 12.1 and it also gives me 2 snapshot ids. Go figure. Anyway, later in the script I re-use that $id and this fails, producing the 2 lines
Ignoring "7276c03d43178fca": no matching ID found for prefix "7276c03d43178fca"
.
Solution: I now use restic snapshots latest --json
, which gives me a single id.
What puzzles me: In the database where I log backups I can clearly see that yesterday, I only got 1 id back from the json. And I sure was not on 0.12, because that one doesn’t know the flag --latest
.
Anyway, that’s demystified (enough for me to call it solved).
Issue 2 - (solved): snapshot made with 0.13 is missing the parent
I had added a new folder to the backup, may that be the reason? (Just saw #2246 on github: Parent-snapshot detection fails with changing --files-from (not through the whole ticket thread yet).
Update: Made some tests (man, the dry-run feature comes in handy*) and it’s indeed just my crappy scripting (issue 1) and the addition of the folder to the backup (issue 2).
* I can’t thank you enough for the dry-run feature. Well, that, and for restic as a whole. 