mirror of
https://github.com/restic/restic.git
synced 2024-12-25 01:06:39 +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. |
||
|---|---|---|
| .. | ||
| 0.6.0_2017-05-29 | ||
| 0.6.1_2017-06-01 | ||
| 0.7.0_2017-07-01 | ||
| 0.7.1_2017-07-22 | ||
| 0.7.2_2017-09-13 | ||
| 0.7.3_2017-09-20 | ||
| 0.8.0_2017-11-26 | ||
| 0.8.1_2017-12-27 | ||
| 0.8.2_2018-02-17 | ||
| 0.8.3_2018-02-26 | ||
| 0.9.0_2018-05-21 | ||
| 0.9.1_2018-06-10 | ||
| 0.9.2_2018-08-06 | ||
| 0.9.3_2018-10-13 | ||
| 0.9.4_2019-01-06 | ||
| 0.9.5_2019-04-23 | ||
| 0.9.6_2019-11-22 | ||
| 0.10.0_2020-09-19 | ||
| 0.11.0_2020-11-05 | ||
| 0.12.0_2021-02-14 | ||
| 0.12.1_2021-08-03 | ||
| unreleased | ||
| changelog-github.tmpl | ||
| CHANGELOG.tmpl | ||
| TEMPLATE | ||