aliases | category | classification | date | date_modified | draft | id | image | links | local_archive_links | pinned | series | tags | title | type | |||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
borg |
public |
2022-10-26 06:49:07 -0700 |
2024-09-23 12:07:10 -0700 |
false |
20221026134907 |
|
false |
false |
|
Borg Backup Item Flags |
tech-note |
When Borg Backup runs each file will show a status character, these are detailed below:
A uppercase character represents the status of a regular file relative to the "files" cache (not relative to the repo -- this is an issue if the files cache is not used). Metadata is stored in any case and for
A
andM
also new data chunks are stored. ForU
all data chunks refer to already existing chunks.
A
= regular file, added (see also I am seeingA
(added) status for an unchanged file!? in the FAQ)M
= regular file, modifiedU
= regular file, unchangedC
= regular file, it changed while we backed it upE
= regular file, an error happened while accessing/reading this fileA lowercase character means a file type other than a regular file, borg usually just stores their metadata:
d
= directoryb
= block devicec
= char deviceh
= regular file, hardlink (to already seen inodes)s
= symlinkf
= fifoOther flags used include:
i
= backup data was read from standard input (stdin)-
= dry run, item was not backed upx
= excluded, item was not backed up?
= missing status code (if you see this, please file a bug report!)— borg create — Borg - Deduplicating Archiver 1.2.3 documentation