- 多台机器备份到同一个仓库:内容定义分块让不同机器、不同版本间的重复数据只存一份,换 rsync 就得每台机器一份完整副本,磁盘占用随机器数线性涨
- 每天定时增量备份大目录(源码树、文档、虚拟机镜像):只传新增块,压缩算法可按仓库选 lz4 换速度或 zstd 换体积,比 tar 全量+轮转省带宽也省空间
- 异地备份走 ssh 或 s3:客户端侧加密,仓库服务器只看到密文,不需要信任托管方;换 restic 也能做到,但 borg 的仓库格式和 prune 语义更老成
- 需要从归档里直接翻单个文件:挂载成用户态文件系统浏览,不用先整包解出来
borg
borgbackup活跃维护 有专家点评去重备份归档工具,支持压缩和认证加密,可通过 SSH 远程备份,适合需要高效增量备份和隐私保护的数据场景。
Deduplicating archiver with compression and authenticated encryption.
专家点评
上手难度:进阶更新于 2026-11-11按内容分块去重的加密备份归档器,在备份链路上顶替 rsync+tar+快照轮转那一套
适用场景
踩坑
- 这是 Borg2 beta 分支:README 明说 beta 之间不保证兼容、升级要删库重建,任何打算长期保留的备份都不该建在这上面,撞上的时机是第一次跨 beta 升级
- 远程仓库走 ssh/http 时,服务端也要装 borg 才能拿到性能收益,只在一端装会退化成低效路径;issue 里 S3/FUSE 远程后端相关的讨论反复出现,说明远程仓库形态一直是摩擦点
- 去重和加密都吃 CPU 与内存,issue 里 Multithreading 被反复提起,单线程处理大仓库时耗时集中在分块与压缩阶段;Windows 支持标注为实验性,跨平台混用前先确认
同类对比
restic 更轻、后端抽象更干净,纯对象存储场景可以优先考虑;需要块级增量快照而非归档文件时看 bup 或文件系统快照方案。
export BORG_REPO=/path/to/repo
borg repo-create --encryption=aes256-ocb --key-location=repokey
borg create docs ~/DocumentsREADME 未说明显存或 GPU 要求;提供 Linux、macOS、FreeBSD、Windows 单文件二进制,无需安装即可运行。
项目说明
由 README 自动翻译提炼去重备份归档工具,按内容分块只存变化,支持压缩与认证加密
去重备份归档工具,支持压缩和认证加密,可通过 SSH 远程备份,适合需要高效增量备份和隐私保护的数据场景。
核心能力
- 用内容定义分块做去重,只存从未出现过的块
- 支持 lz4、zstd、zlib、lzma 多种压缩算法
- 客户端 256 位认证加密,可选 AES-OCB 或 chacha20-poly1305
- 可通过 ssh、http、sftp、s3、rclone 做异地备份
- 备份归档可挂载为用户态文件系统浏览恢复
容易踩的坑
这是 Borg2 beta 分支,beta 之间不保证兼容,升级需删除重建仓库,不要用于生产备份;远程仓库走 ssh/http 时需在仓库服务器上也安装 borg 才能获得性能提升;Windows 支持为实验性。
- 2.0.0b25Release 2.0.0b25pre-release2026-09-27 · 2026-09-27 22:59 UTC
查看更新说明
See the changelog for what changed in this release.
Installation
pip install borgbackup==2.0.0b25, or use one of the standalone binaries below - they contain everything they need and just have to be made executable.For each platform there is a single-file binary (
borg-*-gh,.exeon Windows) and, as a.tgz, the same thing as a directory (borg-dir/borg.exe), which starts up faster.The Linux binaries come in two flavours:
glibc243(built on Ubuntu 26.04) andglibc239(built on Ubuntu 24.04) for systems with an older glibc or with a CPU below x86-64-v3, on which theglibc243x86_64 binary does not run. Your system needs at least the glibc version in the name.The macOS binaries are built without FUSE support, so
borg mountdoes not work with them; install viapipinstead if you need FUSE support.All release assets have a build provenance attestation, verifiable with
gh attestation verify --owner borgbackup <file>.Every attestation is additionally attached as a sigstore bundle
<asset>.sigstore.jsonl, so it can be verified offline and without a GitHub token, e.g. with cosign:cosign verify-blob borgbackup-2.0.0b25.tar.gz \ --bundle borgbackup-2.0.0b25.tar.gz.sigstore.jsonl \ --certificate-identity https://github.com/borgbackup/borg/.github/workflows/release.yml@refs/tags/2.0.0b25 \ --certificate-oidc-issuer https://token.actions.githubusercontent.comThe binaries are built by
ci.yml, not byrelease.yml, so their--certificate-identityishttps://github.com/borgbackup/borg/.github/workflows/ci.yml@refs/tags/2.0.0b25. - 2.0.0b24Release 2.0.0b24pre-release2026-09-02 · 2026-09-02 21:34 UTC
查看更新说明
See the changelog for what changed in this release.
Installation
pip install borgbackup==2.0.0b24, or use one of the standalone binaries below - they contain everything they need and just have to be made executable.For each platform there is a single-file binary (
borg-*-gh,.exeon Windows) and, as a.tgz, the same thing as a directory (borg-dir/borg.exe), which starts up faster.The macOS binaries are built without FUSE support, so
borg mountdoes not work with them; install viapipinstead if you need FUSE support.All release assets have a build provenance attestation, verifiable with
gh attestation verify --owner borgbackup <file>.Every attestation is additionally attached as a sigstore bundle
<asset>.sigstore.jsonl, so it can be verified offline and without a GitHub token, e.g. with cosign:cosign verify-blob borgbackup-2.0.0b24.tar.gz \ --bundle borgbackup-2.0.0b24.tar.gz.sigstore.jsonl \ --certificate-identity https://github.com/borgbackup/borg/.github/workflows/release.yml@refs/tags/2.0.0b24 \ --certificate-oidc-issuer https://token.actions.githubusercontent.comThe binaries are built by
ci.yml, not byrelease.yml, so their--certificate-identityishttps://github.com/borgbackup/borg/.github/workflows/ci.yml@refs/tags/2.0.0b24. - 2.0.0b23Release 2.0.0b23pre-release2026-08-23 · 2026-08-23 14:52 UTC
查看更新说明
borgbackup 2.0.0b23 beta release - do not use this on production backup repositories.
Big changes, please help practically testing them!
Long changelog: https://borgbackup.readthedocs.io/en/2.0.0b23/changes.html#version-2-0-0b23-2026-08-23
If you use pip to install this, use: pip install "borgbackup==2.0.0b23"
Docs: https://borgbackup.readthedocs.io/en/2.0.0b23/
Discussion: https://github.com/borgbackup/borg/discussions/10187
- 2.0.0b22Release 2.0.0b22pre-release2026-07-22 · 2026-07-22 12:43 UTC
查看更新说明
borgbackup 2.0.0b22 beta release - do not use this on production backup repositories.
Big changes, this is the first release with PACKS! So, despite the "beta" release number, rather expect alpha quality / stability.
Read the full story about packs there: https://mrraj.dev/borg
Long changelog: https://borgbackup.readthedocs.io/en/2.0.0b22/changes.html#version-2-0-0b22-2026-07-22
If you use pip to install this, use: pip install "borgbackup==2.0.0b22"
Docs: https://borgbackup.readthedocs.io/en/2.0.0b22/
Discussion: https://github.com/borgbackup/borg/discussions/9926
- 1.4.5Release 1.4.5最新正式版2026-07-18 · 2026-07-18 22:36 UTC
borgbackup 1.4.5
Some fixes (including a low-severity security fix), some new features and other updates.
Long changelog:
https://borgbackup.readthedocs.io/en/1.4.5/changes.html#version-1-4-5-2026-07-19
Short borg 1.4 overview (from a borg 1.2 perspective):
https://www.borgbackup.org/releases/borg-1.4.html
Installation
If you use pip to install this, use: pip install "borgbackup==1.4.5"
For other installation methods and more details, please see: https://borgbackup.org/
See also the 00_README.txt file in the assets list below for a description of the available "fat binary" downloads.
Discussion: https://github.com/borgbackup/borg/discussions/9915
Note:
- *-gh binaries are built on GitHub now. These Linux and FreeBSD binaries do support
borg mount(FUSE filesystem), but the macOS binaries don't (use our brew tap!).
- *-gh binaries are built on GitHub now. These Linux and FreeBSD binaries do support
用户点评
登录用户的真实使用记录,可按版本和硬件筛选还没有人点评。第一个说出真实体验的人最有价值。
This is borg2!
Please note that this is the README for (unstable) Borg2 / master branch.
For general project infos, versioned docs, screen casts, please see there:
Borg2 is currently in beta testing and might get major and/or breaking changes between beta releases (and there is no beta to next-beta upgrade code, so you will have to delete and re-create repos).
Thus, DO NOT USE BORG2 FOR YOUR PRODUCTION BACKUPS! Please help with testing it, but set it up additionally to your production backups.
What is BorgBackup?
BorgBackup (short: Borg) is a deduplicating backup program. Optionally, it supports compression and authenticated encryption.
The main goal of Borg is to provide an efficient and secure way to back up data. The data deduplication technique used makes Borg suitable for daily backups since only changes are stored. The authenticated encryption technique makes it suitable for backups to targets not fully trusted.
See the installation manual_ or, if you have already
downloaded Borg, docs/installation.rst to get started with Borg.
.. _installation manual: https://borgbackup.readthedocs.io/en/master/installation.html
Main features
**Space efficient storage**
Deduplication based on content-defined chunking is used to reduce the number
of bytes stored: each file is split into a number of variable length chunks
and only chunks that have never been seen before are added to the repository.
A chunk is considered duplicate if its id_hash value is identical.
A cryptographically strong hash or MAC function is used as id_hash,
e.g. (hmac-)sha256 or (keyed) blake3.
To deduplicate, all the chunks in the same repository are considered, no
matter whether they come from different machines, from previous backups,
from the same backup or even from the same single file.
Compared to other deduplication approaches, this method does NOT depend on:
* file/directory names staying the same: So you can move your stuff around
without killing the deduplication, even between machines sharing a repo.
* complete files or time stamps staying the same: If a big file changes a
little, only a few new chunks need to be stored - this is great for VMs or
raw disks.
* The absolute position of a data chunk inside a file: Stuff may get shifted
and will still be found by the deduplication algorithm.
Supported chunkers:
* fastcdc (the default)
* buzhash64 (improved), buzhash (as in borg 1.x)
* toeplitz-aes / rabin-aes / goldilocks-aes (keyed, AES-based; they make
chunk-boundary fingerprinting attacks much harder)
* fixed (fixed blocksize, optionally with a differently sized header)
**Speed**
* performance-critical code (chunking, compression, encryption) is
implemented in C/Cython, using SIMD (NEON / AVX2 / AVX-512) where that
is a win - the scan kernel is picked per platform
* local caching
* quick detection of unmodified files
**Data encryption**
All data can be protected client-side using 256-bit authenticated encryption
(AES-OCB or chacha20-poly1305), ensuring data confidentiality, integrity and
authenticity.
If you do not need confidentiality, there are also modes that only
authenticate (``authenticated-sha256`` / ``authenticated-blake3``).
**Hashing**
You can choose between HMAC-SHA256 and Blake3.
**Obfuscation**
Optionally, Borg can actively obfuscate, e.g., the size of files/chunks to
make fingerprinting attacks more difficult.
**Compression**
All data can be optionally compressed:
* lz4 (super fast, low compression)
* zstd (wide range from high speed and low compression to high compression
and lower speed)
* zlib (medium speed and compression)
* lzma (low speed, high compression)
**Off-site backups**
Borg can store data on any remote host accessible via misc. protocols:
* ``ssh://`` (REST-http-over-stdio-over-ssh) and ``http(s)://``
(REST-http-over-tcp). Significant performance gains can be achieved with
these by having a remote agent (borg must be installed on the repo server).
* ``sftp://``
* ``s3://`` / ``b2://``
* ``rclone:`` - lots of protocols / providers supported by rclone
**Backups mountable as file systems**
Backup archives are mountable as user-space file systems for easy interactive
backup examination and restores (e.g., by using a regular file manager).
**Easy installation on multiple platforms**
We offer single-file binaries that do not require installing anything -
you can just run them on these platforms:
* Linux (x86_64, arm64)
* macOS (arm64, x86_64)
* FreeBSD (x86_64)
* Windows (x86_64, MSYS2/MINGW borg.exe, experimental)
Borg also runs on these platforms, but you need to install it from a
package or from source:
* NetBSD (xattrs, but no ACLs)
* OpenBSD (no xattrs/ACLs support)
* illumos / Solaris (xattrs, but no ACLs)
* Cygwin (experimental)
* Windows Subsystem for Linux (WSL) on Windows 10/11 (experimental)
**Free and Open Source Software**
* security and functionality can be audited independently
* licensed under the BSD (3-clause) license, see `License`_ for the
complete license
Easy to use
~~~~~~~~~~~
For ease of use, set the BORG_REPO environment variable::
$ export BORG_REPO=/path/to/repo
Create a new backup repository (see ``borg repo-create --help`` for encryption options)::
$ borg repo-create --encryption=aes256-ocb --key-location=repokey
Create a new backup archive::
$ borg create docs ~/Documents
Now do another backup, just to show off the great deduplication::
$ borg create -v --stats docs ~/Documents
Creating archive "docs" in repository /path/to/repo
Repository: /path/to/repo
Archive name: docs
Archive fingerprint: 7714aef97c1a24539cc3dc73f79b060f14af04e2541da33d54c7ee8e81a00089
Time (nominal): Mon, 2026-08-03 19:57:35 +0200
Time (start): Mon, 2026-08-03 19:57:35 +0200
Time (end): Mon, 2026-08-03 19:57:35 +0200
Duration: 0.01 seconds
Number of files: 24
Original size: 29.73 MB
Deduplicated size: 520 B
...
For demo videos, check out our homepage: https://www.borgbackup.org/#demo
Helping, donations and bounties, becoming a Patron
--------------------------------------------------
Your help is always welcome!
Spread the word, give feedback, help with documentation, testing or development.
You can also give monetary support to the project, see here for details:
https://www.borgbackup.org/#fund
Thanks to everyone who has helped so far - these are the people with the most
commits, see `FAME.md <https://github.com/borgbackup/borg/blob/master/FAME.md>`_
for the full list:
.. image:: https://raw.githubusercontent.com/borgbackup/borg/master/FAME.svg
:alt: Borg contributors by commit count
:target: https://github.com/borgbackup/borg/blob/master/FAME.md
Links
-----
* `Main website <https://www.borgbackup.org/>`_
* `Releases <https://github.com/borgbackup/borg/releases>`_,
`PyPI packages <https://pypi.org/project/borgbackup/>`_ and
`Changelog <https://github.com/borgbackup/borg/blob/master/docs/changes.rst>`_
* `GitHub <https://github.com/borgbackup/borg>`_ and
`Issue tracker <https://github.com/borgbackup/borg/issues>`_.
* `Web chat (IRC) <https://web.libera.chat/#borgbackup>`_ and
`Mailing list <https://mail.python.org/mailman/listinfo/borgbackup>`_
* `License <https://borgbackup.readthedocs.io/en/master/authors.html#license>`_
* `Security contact <https://borgbackup.readthedocs.io/en/master/support.html#security-contact>`_
Compatibility notes
-------------------
EXPECT THAT WE WILL BREAK COMPATIBILITY REPEATEDLY WHEN MAJOR RELEASE NUMBER
CHANGES (like when going from 0.x.y to 1.0.0 or from 1.x.y to 2.0.0).
NOT RELEASED DEVELOPMENT VERSIONS HAVE UNKNOWN COMPATIBILITY PROPERTIES.
THIS IS SOFTWARE IN DEVELOPMENT, DECIDE FOR YOURSELF WHETHER IT FITS YOUR NEEDS.
Security issues should be reported to the `Security contact`_ (or
see ``docs/support.rst`` in the source distribution).
.. start-badges
|doc| |build| |coverage| |bestpractices|
.. |doc| image:: https://readthedocs.org/projects/borgbackup/badge/?version=master
:alt: Documentation
:target: https://borgbackup.readthedocs.io/en/master/
.. |build| image:: https://github.com/borgbackup/borg/actions/workflows/ci.yml/badge.svg?branch=master
:alt: Build Status (master)
:target: https://github.com/borgbackup/borg/actions
.. |coverage| image:: https://codecov.io/github/borgbackup/borg/coverage.svg?branch=master
:alt: Test Coverage
:target: https://codecov.io/github/borgbackup/borg?branch=master
.. |bestpractices| image:: https://www.bestpractices.dev/projects/271/badge
:alt: Best Practices Score
:target: https://www.bestpractices.dev/projects/271
.. end-badges