Repository navigation
⚡️ Feature: Consider vykar as the backup engine (replacing Rustic) #4817
neurekadev
started this conversation in
Feature requests
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Summary
Consider replacing Rustic with vykar as the engine for volume and system backups, once vykar reaches production readiness. vykar is a newer Rust backup tool from BorgBase. In its project benchmark it is much faster than Rustic and uses far less memory.
Why
Results from vykar's v0.22.0 benchmark (raw data). The dataset was 49 GiB in 367k files, backed up to a local repository with comparable zstd levels:
The restore memory peak matters most for Arcane, because many installs run on small NAS boxes and Raspberry Pis. Caveats: this is vykar's own benchmark, the Rustic figure is a single run of an unrecorded version, and the test used local disk only. vykar says S3 performance is the focus of its next release.
Why not yet
Possible approach
backup.Engine, chosen per repository.It may also be worth checking whether Rustic's 5.8 GiB restore peak shows up with Arcane's current Rustic version (v0.11.2) and can be reduced there in the meantime.
AI disclosure: researched and drafted with Claude Code (reading vykar's source, docs, and benchmark data, and Arcane's backup engine), then reviewed and edited by me.
All reactions