Borg: Difference between revisions
From DWIKI
m →FAQ |
Tag: wikieditor |
||
| (44 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
Borg backup | Borg backup | ||
=Links= | = Links = | ||
*[https://borgbackup.readthedocs.io/en/stable/ Homepage] | |||
*[https://github.com/borgbackup/borg/issues/392 support keyring for passphrase storage] | *[https://borgbackup.readthedocs.io/en/stable/ Homepage] | ||
*[https://ci.appveyor.com/project/borgbackup/borg/build/artifacts Borg on windows] | *[https://borgbackup.readthedocs.io/en/stable/faq.html Borg FAQ] | ||
*[https://github.com/borgbackup/borg/issues/392 support keyring for passphrase storage] | |||
*[https://ci.appveyor.com/project/borgbackup/borg/build/artifacts Borg on windows] | |||
*[https://notabug.org/demure/scripts/src/master/borg_wrap.sh A borg script] | |||
*[https://github.com/borgbackup/borg/issues/6602 About upgrading to borg 2] | |||
*[http://www.elho.net/dev/borg/ Someone did some benchmarking] | |||
=Tools= | |||
*[ https://vorta.borgbase.com/ Vorta, a borg backup GUI for Linux and MacOS] | |||
=HOWTO= | |||
==Check repository on server== | |||
borg check --repository-only | |||
does not need key | |||
== Rename repository == | |||
=FAQ= | *On server: rename repository | ||
*On client: change previous_location in ~/.cache/borg/*.config | |||
*BORG_RELOCATED_REPO_ACCESS_IS_OK=yes | |||
==Delete files/directories from repository== | |||
borg recreate --exclude foo/bar myrepo | |||
After that you might want to run | |||
borg compact myrepe | |||
== Extract with pattern == | |||
borg extract server:repo sh:path/to/files.* | |||
==Export key== | |||
==Install using pip== | |||
apt-get install libssl-dev python3-cryptography liblz4-dev libzstd-dev libxxhash-dev libacl1-dev | |||
pip install borgbackup==1.2.0 | |||
==Mount borg archive== | |||
borg mount | |||
===borg mount not available: no FUSE support, BORG_FUSE_IMPL=pyfuse3,llfuse=== | |||
apt install python3-pyfuse3 | |||
= FAQ = | |||
== 4 orphaned objects found! == | |||
A job for borg check | |||
==Borg list only shows checkpoints== | |||
Means the backup wasn't finished. | |||
==Enter passphrase for key== | |||
probably means the BORG_PASSPHRASE | |||
== Remote: Using a pure-python msgpack! This will result in lower performance == | |||
On CentOS: try installing python34-msgpack? | On CentOS: try installing python34-msgpack? | ||
==Connection closed by remote host. Is borg working on the server?== | 'user@borgserver' ? | ||
== Warnings == | |||
=== Killed stale lock === | |||
== Error messages == | |||
===nonce: file changed while we backed it up=== | |||
"bug", this will go away in borg 2, ignore or exclude for now | |||
===does not look like a Borg cache=== | |||
It got corrupted somehow, try | |||
borg delete --cache-only REPO | |||
=== Connection closed by remote host. Is borg working on the server? === | |||
Usually ssh key problem of it means borg is not installed on the server | |||
===Failed to create/acquire the lock=== | |||
Usually the 'timeout' bit is relevant. Just try again later. | |||
Does the backup or source happen to be pretty big? | |||
Also check access rights on the lock file. | |||
=== BlockingIOError: [Errno 11] Resource temporarily unavailable === | |||
windows? | |||
===Corrupted segment reference count - corrupted index or hints=== | |||
For some reason it might help to run | |||
borg check --repository-only | |||
=== Exception: FD exception occurred === | |||
Probably running borg on cygwin, could be ssh key issue. Try | |||
BORG_RSH="ssh -vvv" borg ... | BORG_RSH="ssh -vvv" borg ... | ||
Also check your quotes | |||
=== Cache, or information obtained from the security directory is newer than repository - this is either an attack or unsafe (multiple repos with same ID) === | |||
Something broke during a backup, try (re)moving ~/.config/borg/security/<id> and ~/.cache/borg/<id>. | |||
=== Prune: Chunk ID missing from chunks index, corrupted chunks index - aborting transaction. === | |||
Try | |||
borg check ( --repair ) | |||
If check finds no problem, delete cache: | |||
mv ~/.cache/borg ~/.cache/borg_corrupted | |||
=== ValueError: stats_against: key contained in self but not in master_index. === | |||
Try | |||
borg check ( --repair ) | |||
=== BrokenPipeError: [Errno 32] Broken pipe === | |||
===Remote: Write failed: Broken pipe=== | |||
===The 'borgbackup==1.1.3' distribution was not found and is required by the application=== | |||
Incomplete install? | |||
===Segment not found, but listed in compaction data=== | |||
Try | |||
borg check | |||
and then perhaps | |||
borg check --repair | |||
===Repository path not allowed=== | |||
Server is probably using '''--restrict-to-path''' | |||
==Deduplicated size== | |||
For single archive: total size of unique chunks for this archive | |||
[[Category:Backup]] | |||
Latest revision as of 14:39, 6 February 2026
Borg backup
Links
- Homepage
- Borg FAQ
- support keyring for passphrase storage
- Borg on windows
- A borg script
- About upgrading to borg 2
- Someone did some benchmarking
Tools
- [ https://vorta.borgbase.com/ Vorta, a borg backup GUI for Linux and MacOS]
HOWTO
Check repository on server
borg check --repository-only
does not need key
Rename repository
- On server: rename repository
- On client: change previous_location in ~/.cache/borg/*.config
- BORG_RELOCATED_REPO_ACCESS_IS_OK=yes
Delete files/directories from repository
borg recreate --exclude foo/bar myrepo
After that you might want to run
borg compact myrepe
Extract with pattern
borg extract server:repo sh:path/to/files.*
Export key
Install using pip
apt-get install libssl-dev python3-cryptography liblz4-dev libzstd-dev libxxhash-dev libacl1-dev pip install borgbackup==1.2.0
Mount borg archive
borg mount
borg mount not available: no FUSE support, BORG_FUSE_IMPL=pyfuse3,llfuse
apt install python3-pyfuse3
FAQ
4 orphaned objects found!
A job for borg check
Borg list only shows checkpoints
Means the backup wasn't finished.
Enter passphrase for key
probably means the BORG_PASSPHRASE
Remote: Using a pure-python msgpack! This will result in lower performance
On CentOS: try installing python34-msgpack?
'user@borgserver' ?
Warnings
Killed stale lock
Error messages
nonce: file changed while we backed it up
"bug", this will go away in borg 2, ignore or exclude for now
does not look like a Borg cache
It got corrupted somehow, try
borg delete --cache-only REPO
Connection closed by remote host. Is borg working on the server?
Usually ssh key problem of it means borg is not installed on the server
Failed to create/acquire the lock
Usually the 'timeout' bit is relevant. Just try again later. Does the backup or source happen to be pretty big?
Also check access rights on the lock file.
BlockingIOError: [Errno 11] Resource temporarily unavailable
windows?
Corrupted segment reference count - corrupted index or hints
For some reason it might help to run
borg check --repository-only
Exception: FD exception occurred
Probably running borg on cygwin, could be ssh key issue. Try
BORG_RSH="ssh -vvv" borg ...
Also check your quotes
Cache, or information obtained from the security directory is newer than repository - this is either an attack or unsafe (multiple repos with same ID)
Something broke during a backup, try (re)moving ~/.config/borg/security/<id> and ~/.cache/borg/<id>.
Prune: Chunk ID missing from chunks index, corrupted chunks index - aborting transaction.
Try
borg check ( --repair )
If check finds no problem, delete cache:
mv ~/.cache/borg ~/.cache/borg_corrupted
ValueError: stats_against: key contained in self but not in master_index.
Try
borg check ( --repair )
BrokenPipeError: [Errno 32] Broken pipe
Remote: Write failed: Broken pipe
The 'borgbackup==1.1.3' distribution was not found and is required by the application
Incomplete install?
Segment not found, but listed in compaction data
Try
borg check
and then perhaps
borg check --repair
Repository path not allowed
Server is probably using --restrict-to-path
Deduplicated size
For single archive: total size of unique chunks for this archive
