Versioned Linux file backups from the command line: restic, BorgBackup and Kopia
restic is our Pick for versioned Linux file backups. It reaches the widest range of storage without software on the other end, and no security advisory is on record for it. BorgBackup suits a server you control; Kopia suits people who want policies and a desktop app.
restic
One program that writes encrypted, versioned backups to a local disk, an SFTP login or cloud object storage with nothing installed on the receiving end, in a documented format a second program can also read.
No built-in scheduler. The default check skips stored data, and encryption does not stop someone with storage access deleting backups.
Why restic is our PickTeam behind restic? Get your award badge
No Rising Star selected
Vykar still warns against production backups and comes from an established backup provider. Plakar’s first stable release does not establish its earliest public availability.
Our check covers previously identified candidates; newcomer directories were unavailable.
Who is this article for? Linux users and administrators choosing a command-line tool to keep dated, encrypted copies of files and directories on a local disk, an SSH or SFTP server, or cloud object storage.
About 23 min read
What Preferred Pick, Rising Star and Ready to Rock mean
The quick list
Start with restic for local, SFTP or cloud backups. All three are free and open source. Compare where each can store your backups, what recovery needs and what their 2026 releases change.
All three programs are free, open-source downloads with no account or per-backup charge, checked October 19, 2026. Your costs are the disk or storage service you back up to, its transfer and retained-version charges, and the time to schedule, check and rehearse restores. Licenses: BSD-2-Clause for restic, BSD-3-Clause for BorgBackup, Apache-2.0 for Kopia.
The comparison at a glance
Compare where each repository can live, what recovery needs, how each checks stored data and the 2026 changes that affect it.
restic is our Pick for versioned Linux file backups; BorgBackup and Kopia offer the different strengths explained above. All tools remain selectable.
Hides matching answers for the selected tools. Unknowns and unverified claims stay visible.
| Feature | restic | BorgBackup | Kopia |
|---|---|---|---|
| Best fit | Preferred Pick: versioned backups to a local disk, an SFTP login or cloud object storage | Also consider: a Linux server you control, reachable over SSH, that can run Borg | Also consider: policies that run schedules and maintenance, with an official desktop app |
| Where the repository can live | Local, SFTP (no restic on the server), REST server, S3 and compatible, Azure, Google Cloud, Swift; more through rclone | Local filesystem, or a remote machine running Borg over SSH | Local and network storage, SFTP, WebDAV, S3 and compatible, Azure, B2, Google Cloud; optional repository server |
| What recovery needs | The repository password for any of its keys | The passphrase, plus an exported key for keyfile repositories or as a spare | The repository password; losing it loses the data |
| Checking stored data | Default check skips pack contents; read-data, or numbered subsets over several runs, reads everything | Default check reads all segments with CRC; verify-data adds cryptographic checks | Default verify checks structure and blob presence; 100% file verification downloads and decrypts |
| Protection from a compromised client | REST server append-only mode; use keep-within when pruning such repositories | Append-only set on the repository or enforced by borg serve; a later trusted write removes deleted data | Object locks on S3, Azure or Google Cloud, set at repository creation |
| Scheduling | None built in; use systemd timers, cron or a separate tool and check exit codes | None built in; schedule backups, prune and compact yourself | Built-in schedules while the Kopia server or desktop app runs |
| 2026 changes to plan for | 0.19.0 exits 3 when a source path is missing, instead of 0 | Borg 2 needs a new repository and a borg transfer; the 1.2 series gets no new releases | 0.23.1 fixed a rare data-loss race; 0.23.0 removed LZ4 reading and password-less remote servers |
| Software cost and license | $0; BSD-2-Clause; storage and transfer separate | $0; BSD-3-Clause; receiver and storage separate | $0; Apache-2.0; storage and transfer separate |
Versioned file and directory backups on Linux. Public-source research checked October 19, 2026: no installs, repositories, restores or speed tests by us. All three programs are free and open source; storage, transfer and administration cost extra. Their repositories are not plain copies of your files: recovery needs a compatible program and the password or key. Next substantive review: December 18, 2026, or sooner after a Kopia release, a final Borg 2 release or a new advisory.
All features and sources 22 criteria
Open the groups that matter to you. They compare the same selected tools. “Planned” means future work, not an available feature. Sources include the published conditions.
Destinations and repository model
Show 6 criteria
| Feature | restic | BorgBackup | Kopia |
|---|---|---|---|
| Best fit | Preferred Pick: versioned backups to a local disk, an SFTP login or cloud object storage | Also consider: a Linux server you control, reachable over SSH, that can run Borg | Also consider: policies that run schedules and maintenance, with an official desktop app |
| Where the repository can live | Local, SFTP (no restic on the server), REST server, S3 and compatible, Azure, Google Cloud, Swift; more through rclone | Local filesystem, or a remote machine running Borg over SSH | Local and network storage, SFTP, WebDAV, S3 and compatible, Azure, B2, Google Cloud; optional repository server |
| Cloud object storage | Built in; the manual recommends B2 through its S3-compatible interface | Not in 1.4; Borg 2 betas add S3, B2 and rclone | Built in for S3, Azure, B2 and Google Cloud |
| Other services | Through a separately configured rclone | Not available in stable 1.4 | Through rclone, labelled experimental |
| Versioned content model | Snapshots in a deduplicated repository | Named archives in a deduplicated repository | Snapshots in a deduplicated repository, governed by policies |
| Compression | Repository format 2, the default; restic 0.14.0 or later | Chosen per backup | Set by policy; data written with LZ4 is unreadable from 0.23.0 |
These selected tools have matching answers in this group. Turn off “Show differences only” to see them.
Sources for destinations and repository model
Checked October 19, 2026. restic destinations and repository versions; Borg quick start, stable manual and Borg 2 status; Kopia features, repositories, policies and compression. A listed destination does not prove that your provider or filesystem meets a repository’s requirements. Features are project-documented, not tested by us.
Secrets, recovery and checks
Show 6 criteria
| Feature | restic | BorgBackup | Kopia |
|---|---|---|---|
| What recovery needs | The repository password for any of its keys | The passphrase, plus an exported key for keyfile repositories or as a spare | The repository password; losing it loses the data |
| Sharing access | Several passwords unlock the same master keys; a leaked key needs a full re-encryption to revoke | Shared repository secrets do not isolate archives | Direct access exposes all data; the server limits snapshot lists, not stored content |
| Recover selected files | Restore to a target directory, mount or stream a file; ownership by name since 0.19.0 | Extract into the current directory, mount, or dry-run without writing | Restore selected paths or mount snapshots |
| Checking stored data | Default check skips pack contents; read-data, or numbered subsets over several runs, reads everything | Default check reads all segments with CRC; verify-data adds cryptographic checks | Default verify checks structure and blob presence; 100% file verification downloads and decrypts |
| Protection from a compromised client | REST server append-only mode; use keep-within when pruning such repositories | Append-only set on the repository or enforced by borg serve; a later trusted write removes deleted data | Object locks on S3, Azure or Google Cloud, set at repository creation |
| Other documented capability | Copy snapshots between repositories; a second program, rustic, reads the format | Key export, including a printable paper copy; extract dry run | Experimental error correction at repository creation; multi-user repository server |
These selected tools have matching answers in this group. Turn off “Show differences only” to see them.
Sources for secrets, recovery and checks
restic design document, keys, restore, checks and copying, append-only cautions, REST server and 0.19.0 notes; Borg initialization, extraction, checks and append-only mode; Kopia features, verification, object locks, server limits and error correction. Encryption is not deletion protection, and a data check does not rehearse restoring permissions onto a new machine.
Operation, change and continuity
Show 10 criteria
| Feature | restic | BorgBackup | Kopia |
|---|---|---|---|
| Scheduling | None built in; use systemd timers, cron or a separate tool and check exit codes | None built in; schedule backups, prune and compact yourself | Built-in schedules while the Kopia server or desktop app runs |
| Remove history and reclaim space | forget by policy, then prune unreferenced data | prune archives by policy, then compact the repository | Retention policies; full maintenance removes unused data over later cycles |
| Maintenance owner | Whoever runs prune and check | Whoever runs prune, compact and check | One designated user and host runs automatic maintenance |
| Current release, checked October 19, 2026 | 0.19.1, July 5, 2026 | 1.4.5, July 19, 2026; Borg 2 still in beta (2.0.0b25, September 27) | 0.23.1, June 16, 2026; no release since |
| 2026 changes to plan for | 0.19.0 exits 3 when a source path is missing, instead of 0 | Borg 2 needs a new repository and a borg transfer; the 1.2 series gets no new releases | 0.23.1 fixed a rare data-loss race; 0.23.0 removed LZ4 reading and password-less remote servers |
| Security record | No advisory listed on GitHub or OSV | CVE-2026-62268 (low, crafted archives), fixed in 1.4.5; archives made before 1.2.5 need CVE-2023-36811 upgrade steps | CVE-2026-45695 (critical, password-less server), fixed in 0.23.0; restore-path report unfixed in any release |
| Open report to know about | Restoring over existing hard-linked files can zero unchanged parts; fix proposed | No open report we judged material to stable 1.4 | A snapshot entry named .. can make restore write outside the target; fix proposed |
| Who does most of the work | Michael Eischer wrote most 2026 commits; started by Alexander Neumann | Thomas Waldmann wrote most 2026 commits; contributors credited as the Borg Collective | Julio López wrote most 2026 commits by people |
| Software cost and license | $0; BSD-2-Clause; storage and transfer separate | $0; BSD-3-Clause; receiver and storage separate | $0; Apache-2.0; storage and transfer separate |
| Leaving later | Documented format that rustic also reads; restore with a compatible program and the password | Only Borg reads it; borg transfer moves archives to Borg 2 | Only Kopia reads it; LZ4 data needs 0.22.3 or older to read |
These selected tools have matching answers in this group. Turn off “Show differences only” to see them.
Sources for operation, change and continuity
restic scheduling and exit codes, retention, releases, security page, issue 22085, license and rustic; Borg prune, compact, releases, CVE-2026-62268 advisory, security notes and authors; Kopia maintenance, releases, server advisory, LZ4 removal, issue 5700 and license. Vulnerability lookups used OSV; an empty result is not proof of no vulnerability. Commit shares come from each project’s GitHub record of recent 2026 commits. No storage subscription or support agreement was priced.
What matters when choosing
restic is our Practical Pick for a Linux user or administrator who wants dated, encrypted, deduplicated backups of files and directories on a local disk, an SFTP login or cloud object storage. It is free, runs as a single program and can keep its repository in the widest range of places of the three without installing anything on the receiving end: a local directory, an SFTP server, its own REST server, Amazon S3 and S3-compatible services, Azure, Google Cloud Storage and OpenStack Swift, with other services reachable through rclone. Its repository format is documented, and a second program, rustic, reads and writes the same format, so your backups do not depend on one codebase. Neither restic’s GitHub security page nor the OSV vulnerability database listed an advisory for it on October 19, 2026. Repository destinations, design document, rustic, restic security page, OSV
The most important compromise is that restic leaves the routine work to you. It has no scheduler, so you run it from systemd timers, cron or a separate tool and must act on its exit codes. Its default check confirms the repository’s structure but does not read the stored data; reading everything needs --read-data, or numbered subsets spread over several runs, and that downloads data you may pay to transfer. Removing old snapshots takes two steps, forget and then prune. Encryption is not deletion protection: restic’s design document says it is not designed to stop someone deleting files at the storage location, and that a leaked key cannot be securely revoked without re-encrypting the repository. Scheduling and exit codes, integrity checks, retention, design document
Consider BorgBackup 1.4 if you back up to a Linux machine you control over SSH and can install Borg there. Its default check reads all stored data, and the receiving server can refuse deletions from a compromised client. It cannot write to object storage or to an SFTP-only login, and Borg 2, still in beta on October 19, 2026, uses a new repository format that needs a separate transfer. Consider Kopia if you want policies to run schedules, retention and maintenance for you, with an official desktop app, or object locks on S3, Azure or Google Cloud storage. Check its 2026 record first: 0.23.1 fixed a rare race that could lose data, 0.23.0 fixed a critical flaw in password-less server mode and stopped reading data compressed with the old LZ4 option, and a fix for a reported restore-path flaw had not been released. Borg remote repositories, Borg 2 status, Kopia features, Kopia releases
These are researched judgments from documentation, release records, security advisories and public reports checked October 19, 2026. We did not install any of these programs, create repositories or restore data. All three are free and open source; your costs are storage, transfer and the time to schedule, check and rehearse recovery. Three conditions would change our recommendation: a server you control where Borg can run and you value its full default check (consider BorgBackup), a need for built-in schedules, a desktop app or object locks (consider Kopia), or new evidence of a restic restore or repository defect. Whichever you choose, restore some files into an empty directory before you rely on it, and keep the password and any key file somewhere that survives the loss of the computer. If you only want a plain current copy of a folder on a removable drive, that is a different decision: see our folder-mirroring comparison. A mirror copies deletions too, so it does not keep earlier versions.
restic
Preferred Pick · local, SFTP or cloud destinations
Choose restic for versioned, encrypted file backups from Linux when the destination is a local disk, an SFTP login or cloud object storage. Schedule it yourself, alert on its exit codes and read the stored data with periodic checks.
Reasons to choose it
- Widest range of destinations here, with nothing to install on the receiving end
- Documented repository format that a second program, rustic, also reads
- No advisory listed on GitHub or OSV; 2026 releases fixed a silent-success exit code
What to watch
- No built-in scheduler or policy engine
- Default check does not read stored data; full reads cost time and transfer
- A leaked key cannot be revoked without re-encrypting the repository
restic keeps an encrypted repository of snapshots and reuses stored content between them. It can use an existing SFTP login without restic on the server, a local directory, its REST server, Amazon S3 and S3-compatible services, Backblaze B2, Azure Blob Storage, Google Cloud Storage and OpenStack Swift; other services go through a separately configured rclone. The manual recommends reaching Backblaze B2 through its S3-compatible interface because of error-handling problems in the native B2 library. A listed destination does not prove that every provider or cloud drive behaves well as backup storage. We verified that version 0.19.1, released July 5, 2026, is current and that restic is BSD-2-Clause licensed. Repository preparation, 0.19.1 release notes, license
Its 2026 releases fixed problems that matter to unattended backups. Before 0.19.0, released June 9, 2026, restic exited 0 when a top-level source path was missing, so a script could treat an incomplete backup as a success; it now exits 3. The same release fixed index handling that, in rare cases, could lose information in repositories using the older format 1, added restore --ownership-by-name for restoring onto a machine with different user IDs, and made prune repack small files by default. Exit code 3 also means some source files could not be read and were left out of the snapshot, so your scheduler should alert on it. 0.19.0 release notes, backup exit codes
Read the full restic analysis and sources
The default check validates the repository’s structure, not the stored pack contents. --read-data reads everything, which takes time and may add bandwidth charges. A random percentage subset does not guarantee that every pack is eventually read; numbered subsets such as 1/5 through 5/5 cover the whole repository over five runs. Compression needs repository format 2, the default, which restic 0.14.0 and later can read. Integrity checks, repository versions
Recovery can write a snapshot or selected paths into a target directory, mount a repository for browsing or stream a single file. Restore into a new, empty directory. An open report from September 30, 2026, traced by an outside contributor, says --overwrite if-changed and the default --overwrite always can leave parts of a restored file filled with zeros when an existing target file has more than one hard link, while restic exits 0. A fix had been proposed but not merged by October 19. Restore options, issue 22085
forget removes snapshot references by policy and prune deletes data nothing references; preview both with --dry-run. For protection from a compromised client, restic’s REST server has an append-only mode that refuses deletion. The manual warns that a client able to add snapshots with chosen timestamps can still push legitimate ones out of a --keep-* policy later run by a trusted host, and recommends --keep-within for append-only repositories. Retention and append-only cautions, REST server
A repository can have several passwords, each stored as a key file that unlocks the same master keys. They are not separate private areas, and the design document says a leaked key cannot be securely revoked without re-encrypting the whole repository. Design document, key management
Most of the 2026 commits we counted come from one maintainer, Michael Eischer; Alexander Neumann started the project. rustic, a separate Rust program started by a restic contributor, reads and writes the same repository format and is still below version 1.0; it is an exit route to know about, not a recommendation. Choose Kopia if you want the program itself to own schedules and policies, and BorgBackup if your receiver is a server running Borg. Contributors, rustic
Used restic? Share your experience to help other readers choose.
BorgBackup
Also consider · your own Linux server over SSH
Choose BorgBackup 1.4 when you control a Linux machine reachable over SSH that can run Borg, and want a default check that reads all stored data plus append-only access the server enforces.
Reasons to choose it
- Default check reads every stored segment
- Append-only mode can be enforced from the server side
- Stable 1.4 series with a 2026 security fix
What to watch
- No object-storage or SFTP-only destination in 1.4
- Borg 2 needs a new repository and a transfer
- Extract writes into the current directory
Borg 1.4 stores named archives in a deduplicated repository on a local filesystem or on a remote machine that also runs Borg, reached over SSH. That suits an administrator who controls the receiver; it does not suit someone who has only an S3 bucket or an SFTP-only login. We verified that 1.4.5, released July 19, 2026, is the current stable version and that Borg is BSD-3-Clause licensed. Quick start, stable manual and license, 1.4.5 release
Its strengths are checking and server-side protection. A normal borg check reads all repository segments and checks their size and CRC, so it can detect accidental corruption without an extra option; --verify-data adds cryptographic verification of archive content. A repository can be set to append-only, or borg serve --append-only can enforce that through SSH key settings, so a hacked client cannot permanently delete backups. The manual notes that prune still runs in that mode and that a later normal-mode write from a trusted machine removes deleted data for good, so run borg check --verify-data before pruning. Checks, append-only mode
Read the full BorgBackup analysis and sources
You choose the encryption mode when creating the repository. Repokey modes keep the passphrase-protected key inside the repository; keyfile modes keep it on the client. Export a copy of either for disaster recovery and keep the passphrase: an intact repokey repository already holds its key, but losing a separate keyfile can prevent recovery. Authentication-only and unencrypted modes also exist, so the name Borg does not by itself mean a repository is encrypted. Encryption and key custody
borg extract restores into the current working directory, so change to an empty recovery directory first. Ownership, ACLs and extended attributes depend on the target filesystem and the restoring user’s permissions; --dry-run reads and checks archive data without writing files. Version 1.4.5 fixed CVE-2026-62268, rated low: a crafted archive could make borg extract change or link files outside the extraction directory. Creating such an archive needs repository access and, for encrypted repositories, the key and passphrase. The advisory says the 1.2 series gets no new releases. Extraction, CVE-2026-62268 advisory
Respect the version boundary. Borg 2 is still in testing; its 25th beta was published September 27, 2026. It is not directly compatible with 1.x repositories: archives move with borg transfer, which needs space and time, and commands and scripts change. Its direct S3, B2 and rclone repositories are Borg 2 features and outside this comparison. Repositories created before 1.2.5 also need the upgrade steps in Borg’s notes on CVE-2023-36811; updating the program alone is not enough. Borg 2 status, releases, security and upgrade notes
prune removes archives by retention policy and compact frees the space; schedule and monitor both alongside backup creation, because Borg has no scheduler of its own. Most of the 2026 commits we counted come from Thomas Waldmann; the project credits its contributors as the Borg Collective and offers community support, not a support contract. Choose restic for object storage or an SFTP-only login, and Kopia if built-in policies matter more than Borg’s archive-oriented commands. Prune, compact, authors, support
Used BorgBackup? Share your experience to help other readers choose.
Kopia
Also consider · built-in schedules and a desktop app
Choose Kopia when you want policies to run snapshots, retention and maintenance, an official desktop app or object locks on cloud storage. Run 0.23.1 or later, and restore only from repositories you trust until the restore-path fix ships.
Reasons to choose it
- Policies with built-in schedules and automatic maintenance
- Official desktop app alongside the full command line
- Documented object locks on S3, Azure and Google Cloud
What to watch
- 0.23.1 fixed a rare data-loss race in June 2026
- Versions from 0.23.0 cannot read old LZ4-compressed data
- A reported restore-path flaw had no released fix on October 19
Kopia combines snapshots with policies for when to snapshot, what to exclude, how long to keep and how to compress, set globally or per user, host or path. It has a full command line and an official desktop app. Its destinations include local and network storage, SFTP, WebDAV, S3 and compatible services, Azure, Backblaze B2 and Google Cloud Storage; rclone support is labelled experimental. It encrypts data before upload, and losing the repository password means losing the data. We verified that 0.23.1, released June 16, 2026, is current and that Kopia is Apache-2.0 licensed. Features, repositories, 0.23.1 release notes, license
Its distinct advantages are automation and storage-side locks. Timed snapshots run while the Kopia server or desktop app is running, and maintenance runs automatically, quick roughly hourly and full daily, under one designated user and host. Kopia also documents S3 object locks in compliance mode, set when creating the repository, plus equivalents on Azure and Google Cloud, so stored data cannot be deleted for the lock period. restic’s manual does not document a comparable setting, and Borg 1.4 has no object-storage backend. Full maintenance must run more often than the lock period, and long locks can raise storage bills. Policies and scheduling, maintenance, object locks
Read the full Kopia analysis and sources
Run 0.23.1 or later. The project says 0.23.1 fixes a rare race in index compaction that could lead to data loss and recommends upgrading. Version 0.23.0, released May 12, 2026, fixed CVE-2026-45695, rated critical: a server started without a password accepted unauthenticated requests that could run commands as the Kopia user; Kopia now refuses password-less servers except on the local loopback address. 0.23.1 release notes, compaction issue, server advisory
The same 0.23.0 release removed LZ4 compression, deprecated since 2022. Newer versions cannot read data compressed with LZ4, so a repository holding such data must be restored or repacked with an older version, 0.22.3 or earlier, before upgrading. Do that migration with networking disabled, rather than as a password-less server. Compression, LZ4 removal, 0.23.0 release notes
One reported flaw was unfixed in any release on October 19, 2026. A security report filed August 15 and published as an issue on October 9 says a snapshot containing a directory entry named .. makes kopia restore write outside the chosen target. It matters when other people can write snapshots to a repository you restore from. A fix was proposed on October 15 but not merged, and Kopia had not published a release since June 16. Issue 5700, proposed fix
Default kopia snapshot verify checks structure and that stored blobs exist; --verify-files-percent=100 downloads, decrypts and decompresses every file. Kopia requires storage with strong read-after-write consistency and reasonably synchronized clocks; its documentation says large clock differences can make it delete data it considers unneeded. Its Reed-Solomon error correction is labelled experimental and must be enabled when the repository is created; we give it no reliability credit. Verification and consistency, error correction
The optional repository server holds the storage credentials and limits each user to their own snapshot and policy lists, but anyone who knows a valid object ID can restore its contents. Do not treat it as isolation between mutually untrusted users. Most of the 2026 commits by people come from one maintainer, Julio López. Choose restic if you prefer explicit commands and fewer maintenance assumptions, and BorgBackup if your receiver is a server you control. Repository server, security advisories
Used Kopia? Share your experience to help other readers choose.
Which product are we missing?
Know a product that belongs in this article? Tell us what it does differently and why it deserves a closer look. Newcomers welcome.
Readers and product teams can suggest candidates. Suggestions inform our research; they do not guarantee inclusion or a recommendation.
Opens an email draft with this article attached as a link. Nothing is sent until you send it.
No email app? Send the product name, website, and this article’s title to admin@practicalpicks.guide.
What people are saying
Public discussion is a check on project claims, not a measured reliability score. An October 14, 2026 restic report describes scheduled jobs, run through a third-party web front end and rclone to the pCloud service, that reported success while a later check found truncated pack files, several times since August. The reporter repaired the repository and links the cause to an rclone and pCloud interaction reported before, so it is not evidence of a restic defect. It shows why a success message is not proof that data was stored correctly. restic issue 22116
A February 2026 EndeavourOS discussion, last read September 7, 2026, reports problems reintroducing missing Kopia data after repository damage. It links an earlier Kopia support thread, so the two are not independent confirmations, and we cannot tell whether it shares a cause with the later compaction fix. An April 2024 self-hosting discussion praises restic and Kopia after a home-NAS trial, with timings under individual settings, and a 2022 Borg and restic discussion shows how quickly version-specific claims go stale. These self-selected reports do not support a rating or a speed ranking.
Our October 19 search for vulnerabilities, data-loss reports, shutdowns and disputes involving the three projects found nothing beyond the items in this article that changed our conclusions. A search that finds nothing is not proof that nothing exists.
How we researched
This is public-source research. We did not install or run any of these programs, create repositories, use credentials, back up or restore files, or run retention, repair or deletion commands. No project supplied access, payment or input, and we use no affiliate links. We first compared restic, BorgBackup and Kopia on September 7, 2026, and rechecked every material claim on October 19, 2026: releases, licenses, documented destinations, checks, key handling, retention, security advisories and recent issue reports. We read project manuals, release notes, restic’s design document, GitHub security advisories and issue trackers, the OSV vulnerability database and community discussions.
We wrote this for a Linux user or administrator keeping dated, encrypted copies of files and directories on a local disk, a server or cloud storage, using a command-line tool. We fixed five criteria and their weights before comparing: where the repository can live without extra server software (25%), recovery and verification (25%), change and maintenance risk (25%), routine operation such as scheduling and cleanup (15%), and the ability to leave later (10%). restic scored highest. Giving routine operation much more weight brings Kopia close without overtaking it, and a reader whose receiver already runs Borg narrows the gap with BorgBackup. We did not compare whole-disk imaging, Borg 2 betas or storage providers; our Windows comparison covers a different platform and workflow.
We checked project documentation and release records again on November 1, 2026. We have not selected a Rising Star. Vykar still warns against production backups and comes from BorgBase, an established backup provider. Plakar’s release and tag history does not establish its earliest public release date; our earlier research records an older alpha, and a 2025 stable release does not establish eligibility. A connector sign-in or source build, and a lack of independent reviews, are not by themselves reasons to reject it. Backrest and Zerobyte provide web interfaces around restic; rustic, Duplicacy, Duplicati and bupstash predate the newcomer window. Directory discovery was unavailable, so this was a check of previously identified candidates rather than a complete survey of new launches.
We also considered rustic, Duplicacy, Duplicati and Plakar as established alternatives. Their documentation did not establish enough about recovery checks and maintenance risks to score all five criteria on the same basis as the three compared here. We have no complete score for those alternatives and make no ranking claim about them. We could not confirm comparable storage and transfer prices for every alternative.
| Tool | Public sources | What remains uncertain |
|---|---|---|
| restic | Manual, design document, 0.19.0 and 0.19.1 release notes, REST server documentation, license, security page, OSV, issue tracker. | Restore success and speed in your environment, the open hard-link restore report, long-term maintenance by a small team. |
| BorgBackup | Stable 1.4.5 manual, release notes, security advisories, Borg 2 status page, authors and support pages. | Metadata fidelity on your filesystem, when Borg 2 becomes final, how long 1.4 will receive fixes after that. |
| Newcomers and alternatives | Project source, manuals, release records and legal pages, including Vykar, rustic, Duplicacy, Duplicati and Plakar, checked November 1, 2026. | Directory discovery unavailable; Plakar’s earliest public release date, comparable storage costs and alternatives’ full recovery-check and maintenance details remain unknown. |
| Kopia | Features, repository, maintenance, consistency, compression, object-lock and server documentation, release notes, advisories, issue tracker. | When the restore-path fix ships, recovery after repository damage, behavior of the next release. |
Before adopting one, back up some non-sensitive practice files and restore them into an empty directory. Include a file changed between two backups, check the earlier version’s contents and permissions, and confirm you can recover when the original computer and its saved configuration are unavailable. Keep a second copy that the backup client cannot delete. Next substantive review is due December 18, 2026, or sooner after a Kopia release, a final Borg 2 release or a new advisory for any of the three. Found a changed release or behavior? Contact the editors.
Sources and evidence
Sources were checked October 19, 2026 unless another date is given. Project material establishes documented features, published releases and the projects’ own statements, not behavior in your environment. Advisories and issue reports are the projects’ and reporters’ records; we did not reproduce them. Community posts are attributed opinions, not representative samples.
- restic: repository preparation and destinations; backups, exit codes and scheduling; repository operations and integrity checks; restore; retention and append-only cautions; key management; design document; releases, including 0.19.0, June 9, 2026 and 0.19.1, July 5, 2026; REST server; license; security page; contributors; hard-link restore report, September 30, 2026; rustic.
- BorgBackup: stable 1.4.5 manual and license; quick start; initialization and key modes; extract; check; prune; compact; append-only mode; changes and security notes; 1.4.5 release, July 19, 2026; releases including 2.0.0b25, September 27, 2026; CVE-2026-62268 advisory, August 26, 2026; Borg 2 status; authors; support.
- Kopia: features; policies and scheduling; repositories; verification and consistency; maintenance; compression and LZ4 removal; object locks; experimental error correction; repository server; releases, including 0.23.0, May 12, 2026 and 0.23.1, June 16, 2026; compaction data-loss issue; LZ4 removal change; server advisory, May 13, 2026; credential-output advisory, April 9, 2024; restore-path report, published October 9, 2026 and proposed fix; license.
- Vulnerability records: OSV package queries for restic, Kopia and borgbackup.
- Community reports: truncated packs with rclone and pCloud, October 14, 2026; Kopia missing-data discussion, February 2026, last read September 7, 2026; home-NAS experience, April 2024 and Borg and restic discussion, 2022, both last read September 7, 2026. Reports remain unverified and are not representative samples.
This is a researched comparison, not a product review. Commit counts come from the GitHub record of each project’s recent 2026 commits. Storage providers’ terms, charges and deletion controls are a separate decision; we do not endorse a hosting provider. Method: evidence standard, editorial picks.