borg [common options] tag [options] [NAME]
positional arguments |
||
|
specify the archive name |
|
optional arguments |
||
|
set tags (can be given multiple times) |
|
|
add tags (can be given multiple times) |
|
|
remove tags (can be given multiple times) |
|
Archive filters — Archive filters can be applied to repository targets. |
||
|
only consider archives matching all patterns. see “borg help match-archives”. |
|
|
Comma-separated list of sorting keys; valid keys are: timestamp, archive, name, id, tags, host, user; default is: timestamp |
|
|
consider first N archives after other filters were applied |
|
|
consider last N archives after other filters were applied |
|
|
consider archives between the oldest archive’s timestamp and (oldest + TIMESPAN), e.g. 7d or 12m. |
|
|
consider archives between the newest archive’s timestamp and (newest - TIMESPAN), e.g. 7d or 12m. |
|
|
consider archives older than (now - TIMESPAN), e.g. 7d or 12m. |
|
|
consider archives newer than (now - TIMESPAN), e.g. 7d or 12m. |
Manage archive tags.
Borg archives can have a set of tags which can be used for matching archives.
You can set the tags to a specific set of tags or you can add or remove tags from the current set of tags.
User defined tags must not start with @ because such tags are considered special and users are only allowed to use known special tags:
@PROT
: protects archives against archive deletion or pruning.
Pre-existing special tags can not be removed via --set
. You can still use
--set
, but you must give pre-existing special tags also (so they won’t be
removed).