Backup and disaster recovery¶

Backup and disaster recovery is an optional service. If you don't order it, you're responsible for backing up your own applications and data - for example with Velero for Kubernetes resources and persistent volumes. Establish backup schedules and test recovery procedures regularly.

If you use Sunet's S3-compatible object storage or block storage for application data, note that these services are not backed up by default. Plan your own backup strategy accordingly.

What to back up¶

Cluster state. Your Git repository already describes your applications, so a healthy GitOps setup is most of your disaster recovery: re-point a fresh cluster at the repo and ArgoCD rebuilds your workloads. Make sure secrets are recoverable too (your Sealed Secrets are in Git, but the controller's key is in the cluster).
Persistent volume data. Application data on block storage is not in Git. Back it up with Velero (which can snapshot volumes) or at the application level, for example database dumps written to object storage.
Object storage. Replicate critical buckets elsewhere, or use versioning and lifecycle rules. See the Ceph durability reference.

If you order the backup add-on, we run scheduled Velero backups and work with you to determine the right schedule, retention, and recovery plan for your applications.