vaskozl
commented
9 months ago Hyperbackup can only backup LUNs to other NAS and even then I don't think there is a sane way to restore matching PV/PVCs.
Importantly snapshots are supported which enables you to use e.g. velero, volsync or k10 to backup to object storage via the snapshots.
As a user I've decided that I don't really expect more from the CSI itself and the backups can be done with a seperate k8s operator utilising the snapshots.
Other solutions like Ceph or cloud providers are similar in that way. I think maybe only longhorn provides backups/restore itself, but there's no reason to not use one of the few good solutions already out there.
My Synology shows many more "volumes"/LUNs created using the Synology CSI than I have stateful sets and they are named arbitrarily. The result is a "black box" of storage that I am unable to reason about for purposes of backup and restore or even cleaning up.
It would be helpful if documentation provided clear instructions for backing up and restoring volumes in cases of, for example, cluster failure.
Questions I have:
With Docker Compose, it is easy to reason about mounted volumes, especially when using bind mounts: such and such is the specified mounted volume and backup can be as simple as a single rsync command.