mirror of
https://github.com/octoleo/restic.git
synced 2024-06-03 17:40:53 +00:00
058dfc20da
Currently, `restic backup` (if a `--parent` is not provided) will choose the most recent matching snapshot as the parent snapshot. This makes sense in the usual case, where we tag the snapshot-being-created with the current time. However, this doesn't make sense if the user has passed `--time` and is currently creating a snapshot older than the latest snapshot. Instead, choose the most recent snapshot which is not newer than the snapshot-being-created's timestamp, to avoid any time travel. Impetus for this change: I'm using restic for the first time! I have a number of existing BTRFS snapshots I am backing up via restic to serve as my initial set of backups. I initially `restic backup`'d the most recent snapshot to test, then started backing up each of the other snapshots. I noticed in `restic cat snapshot <id>` output that all the remaining snapshots have the most recent as the parent.
13 lines
519 B
Plaintext
13 lines
519 B
Plaintext
Bugfix: Avoid choosing parent snapshots newer than time of current snapshot
|
|
|
|
`restic backup` (if a `--parent` is not provided)
|
|
previously chose the most recent matching snapshot as the parent snapshot.
|
|
However, this didn't make sense when the user passed `--time`
|
|
to create a snapshot older than the most recent snapshot.
|
|
|
|
Instead, `restic backup` now chooses the most recent snapshot
|
|
which is not newer than the snapshot-being-created's timestamp,
|
|
to avoid any time travel.
|
|
|
|
https://github.com/restic/restic/pull/3619
|