Decentralized Backup Tools
Redundant backups spread across independent peers instead of one provider's snapshot system.
Partial overlap. Volume snapshots commit only when 2 replicas return signed evidence and are restored from peers after host loss; control-plane backups are signed and verify offline. There is no off-cluster backup target, and `dh volume snapshot`/`restore` commands are not implemented yet.
How this differs from a normal cloud backup
A normal backup (a cloud snapshot, an S3 bucket) still has one company as the custodian -- if their infrastructure fails catastrophically or they go out of business, your backup can go with it. Decentralized backup tools (Storj, Sia, or IPFS+Filecoin used specifically for backup) spread encrypted, redundant copies across many independent storage providers, so no single provider's failure takes out your backup -- the tradeoff is usually restore speed (reassembling from many peers can be slower than pulling from one fast cloud provider) and more moving parts to get right.
Redundant backups spread across independent peers instead of one provider's snapshot system. Partial overlap. Volume snapshots commit only when 2 replicas return signed evidence and are restored from peers after host loss; control-plane backups are signed and verify offline. There is no off-cluster backup target, and `dh volume snapshot`/`restore` commands are not implemented yet.