We're transitioning our company to use Kubernetes as the main software platform and are seeing great benefits like autonomous service deployment. However, we're facing a challenge with backup solutions, particularly for our databases running as StatefulSets. We're considering Kasten K10 and Velero, but managing database backups and especially point-in-time restores has proven to be a struggle. It feels like we might be hitting a fundamental limitation. Has anyone here dealt with this, and what solutions have worked for you?
5 Answers
Make sure you're using the right database tools for backing up your databases. They can handle the specifics better than a general tool.
Velero has its limitations with StatefulSets due to a lack of application awareness in volume snapshots. You should implement pre-hooks for consistent dumps within your database. Kasten has native support for this, which could simplify things. What specific databases are you running?
For our Postgres databases on Kubernetes, we use the barman cloud plugin with the CNPG operator. It makes point-in-time recovery really straightforward. If you're using Postgres, I suggest checking out that plugin's sidecar container for easy integration.
Honestly, running databases in Kubernetes for production can be tricky. I'd recommend using an operator like CNPG for Postgres, which offers point-in-time recovery and full backup capabilities without much hassle.
Have you tried Volsync? It’s a solid option if you're also doing GitOps. It excels with data-only backups and restores.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures