| 123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104 | 
							- .\" Man page generated from reStructuredText.
 
- .
 
- .TH BORG-COMPRESSION 1 "2020-03-07" "" "borg backup tool"
 
- .SH NAME
 
- borg-compression \- Details regarding compression
 
- .
 
- .nr rst2man-indent-level 0
 
- .
 
- .de1 rstReportMargin
 
- \\$1 \\n[an-margin]
 
- level \\n[rst2man-indent-level]
 
- level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
 
- -
 
- \\n[rst2man-indent0]
 
- \\n[rst2man-indent1]
 
- \\n[rst2man-indent2]
 
- ..
 
- .de1 INDENT
 
- .\" .rstReportMargin pre:
 
- . RS \\$1
 
- . nr rst2man-indent\\n[rst2man-indent-level] \\n[an-margin]
 
- . nr rst2man-indent-level +1
 
- .\" .rstReportMargin post:
 
- ..
 
- .de UNINDENT
 
- . RE
 
- .\" indent \\n[an-margin]
 
- .\" old: \\n[rst2man-indent\\n[rst2man-indent-level]]
 
- .nr rst2man-indent-level -1
 
- .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
 
- .in \\n[rst2man-indent\\n[rst2man-indent-level]]u
 
- ..
 
- .SH DESCRIPTION
 
- .sp
 
- It is no problem to mix different compression methods in one repo,
 
- deduplication is done on the source data chunks (not on the compressed
 
- or encrypted data).
 
- .sp
 
- If some specific chunk was once compressed and stored into the repo, creating
 
- another backup that also uses this chunk will not change the stored chunk.
 
- So if you use different compression specs for the backups, whichever stores a
 
- chunk first determines its compression. See also borg recreate.
 
- .sp
 
- Compression is lz4 by default. If you want something else, you have to specify what you want.
 
- .sp
 
- Valid compression specifiers are:
 
- .INDENT 0.0
 
- .TP
 
- .B none
 
- Do not compress.
 
- .TP
 
- .B lz4
 
- Use lz4 compression. Very high speed, very low compression. (default)
 
- .TP
 
- .B zstd[,L]
 
- Use zstd ("zstandard") compression, a modern wide\-range algorithm.
 
- If you do not explicitely give the compression level L (ranging from 1
 
- to 22), it will use level 3.
 
- Archives compressed with zstd are not compatible with borg < 1.1.4.
 
- .TP
 
- .B zlib[,L]
 
- Use zlib ("gz") compression. Medium speed, medium compression.
 
- If you do not explicitely give the compression level L (ranging from 0
 
- to 9), it will use level 6.
 
- Giving level 0 (means "no compression", but still has zlib protocol
 
- overhead) is usually pointless, you better use "none" compression.
 
- .TP
 
- .B lzma[,L]
 
- Use lzma ("xz") compression. Low speed, high compression.
 
- If you do not explicitely give the compression level L (ranging from 0
 
- to 9), it will use level 6.
 
- Giving levels above 6 is pointless and counterproductive because it does
 
- not compress better due to the buffer size used by borg \- but it wastes
 
- lots of CPU cycles and RAM.
 
- .TP
 
- .B auto,C[,L]
 
- Use a built\-in heuristic to decide per chunk whether to compress or not.
 
- The heuristic tries with lz4 whether the data is compressible.
 
- For incompressible data, it will not use compression (uses "none").
 
- For compressible data, it uses the given C[,L] compression \- with C[,L]
 
- being any valid compression specifier.
 
- .UNINDENT
 
- .sp
 
- Examples:
 
- .INDENT 0.0
 
- .INDENT 3.5
 
- .sp
 
- .nf
 
- .ft C
 
- borg create \-\-compression lz4 REPO::ARCHIVE data
 
- borg create \-\-compression zstd REPO::ARCHIVE data
 
- borg create \-\-compression zstd,10 REPO::ARCHIVE data
 
- borg create \-\-compression zlib REPO::ARCHIVE data
 
- borg create \-\-compression zlib,1 REPO::ARCHIVE data
 
- borg create \-\-compression auto,lzma,6 REPO::ARCHIVE data
 
- borg create \-\-compression auto,lzma ...
 
- .ft P
 
- .fi
 
- .UNINDENT
 
- .UNINDENT
 
- .SH AUTHOR
 
- The Borg Collective
 
- .\" Generated by docutils manpage writer.
 
- .
 
 
  |