BorgBackup
BorgBackup 1.4.5 is a command-line tool for deduplicated, compressed and encrypted backups, designed around repositories that can be checked and restored.
What BorgBackup provides
BorgBackup stores deduplicated, compressed and encrypted archives in a repository. A successful backup command is only one part of a reliable workflow; repository checks, archive listings and an isolated restore test prove that the data can be recovered.
Keys and repository storage
Encryption depends on a key or passphrase, so recovery material should be stored offline and separately from the source data. A cloud-sync folder, mounted drive or remote filesystem may differ in locking, latency and consistency; validate a small repository before using it for production.
Scheduling and retention
Add scheduling only after manual create, check and restore operations are repeatable. Keep retention rules explicit and monitor repository space, source changes and failed jobs. Review date: 2026-08-23.
Save to your cloud drive
Open the cloud drive to get the file directly, or save it for convenient access on another device.
Quark Cloud Drive
RecommendedSave BorgBackup to this cloud drive
Baidu Netdisk
Save BorgBackup to this cloud drive
BorgBackup 1.4.5 repository and restore guide
Create a small encrypted repository, verify the key, make an archive, check it and restore representative files before adding the command to a schedule.
Before you start
- Choose the macOS arm64, macOS x64 or Linux x64 package and confirm the command-line binary runs.
- Prepare a source directory, an independent repository path and offline key storage.
- Select test files with normal names, long paths and large content for restore acceptance.
Installation steps
- 01
Install and verify the binary
Place the package in a controlled path, check the version and run a harmless help or info command before initializing a repository.
- 02
Initialize an encrypted repository
Choose the repository mode, create a strong passphrase and save recovery material separately from the source and repository.
- 03
Create and inspect an archive
Archive the test source, list its contents and note compression, deduplication and exclusion behavior before scheduling it.
Quick start
- 01
Check the repository
Run the repository check and review errors or warnings before considering the archive complete.
- 02
Restore to an isolated directory
Extract representative files into a new directory and compare content, permissions, timestamps and checksums.
- 03
Add a scheduled job
Schedule only after manual runs pass, define retention and log the repository path, key location, last success and free space.
Usage tips
- Repository passwords and keys are part of the recovery plan, not ordinary configuration.
- A synchronized folder is not automatically a consistent backup repository.
- Periodic restore tests matter more than a green command exit alone.
Troubleshooting and uninstall
Can a lost repository passphrase be recovered?
Encryption depends on the key or passphrase. Keep independent recovery material and test it before the only copy is needed.
Why does a remote or cloud repository behave inconsistently?
Check locking, latency, mount reliability and synchronization conflicts. Reproduce the workflow on a small local repository before changing production storage.
- Verify the backup before removalRun a check, restore sample files and record the repository and key locations before uninstalling the binary.
- Remove the tool without deleting the repositoryRemove the executable and scheduled jobs through the operating system, keeping the repository and recovery material until a replacement is verified.
Frequently asked questions
How do I know a Borg archive can be restored?
Run repository checks, list archives and restore representative files into an isolated directory, then compare permissions, timestamps and checksums.
Can I place a Borg repository in a cloud-sync folder?
Test a small repository first. Locking, latency and consistency differ by client and mount, so a sync folder should not be assumed to be a reliable repository.
Does the download require an extraction code?
The Quark entry does not require one; the four-character code for the Baidu entry is shown beside its download entry.