mirror of
https://github.com/restic/restic.git
synced 2024-12-25 09:18:55 +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. |
||
|---|---|---|
| .. | ||
| .gitignore | ||
| issue-1542 | ||
| issue-2202 | ||
| issue-2345 | ||
| issue-2388 | ||
| issue-2656 | ||
| issue-2738 | ||
| issue-3382 | ||
| issue-3464 | ||
| issue-3490 | ||
| issue-3518 | ||
| issue-3541 | ||
| issue-3542 | ||
| issue-3556 | ||
| issue-3601 | ||
| pull-2594 | ||
| pull-2880 | ||
| pull-3429 | ||
| pull-3436 | ||
| pull-3488 | ||
| pull-3508 | ||
| pull-3514 | ||
| pull-3519 | ||
| pull-3591 | ||
| pull-3593 | ||
| pull-3619 | ||