2
2
mirror of https://github.com/octoleo/restic.git synced 2024-11-24 21:57:41 +00:00

Add a note that the oldest snapshot may be kept additionally

Documentation enhancement.
This commit is contained in:
Joram Berger 2023-12-18 18:24:57 +01:00 committed by GitHub
parent b72de5a883
commit 12af20e606
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -207,10 +207,13 @@ The ``forget`` command accepts the following policy options:
They also only count hours/days/weeks/etc which have one or more snapshots. They also only count hours/days/weeks/etc which have one or more snapshots.
A value of ``-1`` will be interpreted as "forever", i.e. "keep all". A value of ``-1`` will be interpreted as "forever", i.e. "keep all".
.. note:: All duration related options (``--keep-{within,-*}``) ignore snapshots .. note:: All duration related options (``--keep-{within-,}*``) ignore snapshots
with a timestamp in the future (relative to when the ``forget`` command is with a timestamp in the future (relative to when the ``forget`` command is
run) and these snapshots will hence not be removed. run) and these snapshots will hence not be removed.
.. note:: If there are not enough snapshots to keep one for each duration related
``--keep-{within-,}*`` option, the oldest snapshot is kept additionally.
.. note:: Specifying ``--keep-tag ''`` will match untagged snapshots only. .. note:: Specifying ``--keep-tag ''`` will match untagged snapshots only.
When ``forget`` is run with a policy, restic first loads the list of all snapshots When ``forget`` is run with a policy, restic first loads the list of all snapshots