VolSync

VolSync is a Kubernetes operator that asynchronously replicates persistent volumes with rsync or rclone and creates restic backups for data protection across…

  • Backup
  • Cloud
  • Tools & Utilities
VolSync is a Kubernetes operator that asynchronously replicates persistent volumes with rsync or rclone and creates restic backups for data protection across clusters and storage systems.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

59/100 Fair

Maintained
100last commit 22 days ago
Popular
601,048 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data
Security check
07 serious findings, 5 minor, CI, tests, OpenSSF Scorecard 6.3/10

Based on 4 of 5 factors.

Availability: platform listings confirmed today

GitHub stars
1,048
Open issues
93
Last commit
2026-10-30
Latest release
v0.17.0
License
AGPL-3.0
Activity
rising

Checked 16 days ago - source: GitHub (backube/volsync)

Resources & Compatibility

Requirements not published yet.

Checked 23 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Install the VolSync operator with Helm If you use Helm (a package manager for Kubernetes), add the Backube repo and install the VolSync chart in a `volsync-system` namespace; without this operator, VolSync is not actually running in your cluster to manage your volume copies. source
  • Allow the rclone mover in destination namespaces For rclone-based copies, set the destination namespace `volsync.backube/privileged-movers` to `true` and add the rclone secret before deploying the destination; without this, the privileged mover cannot start and the copy job fails. source
  • Add the kubectl plugin if you want a CLI If you have Krew (a plugin manager for kubectl), run `kubectl krew install volsync` so you can check and manage VolSync with `kubectl volsync`; this is a handy extra, but it is not required for the cluster operator to work. source

Fetched 53 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How do I get VolSync running in a Kubernetes cluster?

Install the VolSync operator with Helm by adding the Backube repo and deploying the VolSync chart into a volsync-system namespace. Without the operator, VolSync is not running in the cluster to manage volume copies.

Why might a VolSync rclone copy fail in the destination namespace?

For rclone-based copies, set the destination namespace's volsync.backube/privileged-movers to true. Add the rclone secret before deploying the destination, otherwise the privileged mover cannot start and the copy job fails.

Can VolSync safely back up database persistent volumes?

VolSync behaves like snapshot or export for many workloads. Databases could require an actual dump or extra care.

Where should I look when a VolSync restore operation fails?

Check VolSync's detailed error reporting, which appears when restore operations encounter issues. The enhanced reporting provides diagnostic information to help identify and resolve the problem.

Answers sourced from burgdev.github.io, volsync.readthedocs.io, volsync.readthedocs.io, www.reddit.com

Community

Collected 48 days ago - public community threads