mirror of
https://github.com/borgbackup/borg.git
synced 2025-02-25 23:43:49 +00:00
docs: pruning interprets timestamps in the local timezone where borg prune runs
This commit is contained in:
parent
0e577452c2
commit
2b1303d280
1 changed files with 6 additions and 6 deletions
|
@ -214,12 +214,12 @@ def build_parser_prune(self, subparsers, common_parser, mid_common_parser):
|
|||
up to 7 most recent days with backups (days without backups do not count).
|
||||
The rules are applied from secondly to yearly, and backups selected by previous
|
||||
rules do not count towards those of later rules. The time that each backup
|
||||
starts is used for pruning purposes. Dates and times are interpreted in
|
||||
the local timezone, and weeks go from Monday to Sunday. Specifying a
|
||||
negative number of archives to keep means that there is no limit. As of borg
|
||||
1.2.0, borg will retain the oldest archive if any of the secondly, minutely,
|
||||
hourly, daily, weekly, monthly, or yearly rules was not otherwise able to meet
|
||||
its retention target. This enables the first chronological archive to continue
|
||||
starts is used for pruning purposes. Dates and times are interpreted in the local
|
||||
timezone of the system where borg prune runs, and weeks go from Monday to Sunday.
|
||||
Specifying a negative number of archives to keep means that there is no limit.
|
||||
As of borg 1.2.0, borg will retain the oldest archive if any of the secondly,
|
||||
minutely, hourly, daily, weekly, monthly, or yearly rules was not otherwise able to
|
||||
meet its retention target. This enables the first chronological archive to continue
|
||||
aging until it is replaced by a newer archive that meets the retention criteria.
|
||||
|
||||
The ``--keep-last N`` option is doing the same as ``--keep-secondly N`` (and it will
|
||||
|
|
Loading…
Reference in a new issue