Parcourir la source

docs: pruning interprets timestamps in the local timezone where borg prune runs

Thomas Waldmann il y a 2 ans
Parent
commit
2b1303d280
1 fichiers modifiés avec 6 ajouts et 6 suppressions
  1. 6 6
      src/borg/archiver/prune_cmd.py

+ 6 - 6
src/borg/archiver/prune_cmd.py

@@ -214,12 +214,12 @@ class PruneMixIn:
         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