PostgreSQL Backup and Restore on Amazon Web Services using Kasten K10
In this blog post we will walk through how to use Kasten K10 to backup and restore PostgreSQL databases operating in a Kubernetes environment on AWS. This blog assumes the use of Amazon Elastic Kubernetes Service (EKS).
EKS is a fully managed Kubernetes service with deep integrations with a multitude of Amazon services making it easy to use and manage. Further, it uses upstream Kubernetes allowing you to use open source community tools and run standard Kubernetes applications without needing refactoring.
PostgreSQL (often referred to as Postgres), is an Open Source relational database, popular in the cloud-native community.
Kasten’s K10 data management platform, it is a secure software-only product that has been purpose-built for Kubernetes and provides operations teams an easy-to-use, scalable, and secure system for backup/restore, disaster recovery, and mobility of Kubernetes applications.
The instructions in this post are organized in three sections:
Installing Kasten K10 on your EKS cluster
Backup and restore workflow using Kasten K10
1. Installing Kasten K10 on Your EKS Cluster
Detailed instructions for installing K10 are available in the K10 documentation. In this post a “happy path” install is used for demo purposes. Before proceeding with the install, the install prerequisites (Helm package manager and Kasten Helm charts repository) need to be satisfied. The Helm commands use Helm v3, but using Helm v2 is also straightforward.
Add the Kasten Helm charts repository and create the namespace where K10 will be installed using the commands below.
To validate the PostgreSQL install, use the command below in the postgresql namespace to confirm that all PostgreSQL pods display a status of Running within a couple of minutes.
$ kubectl get pods --namespace postgresql
K10 automatically discovers the instance of PostgreSQL. Following the successful install of PostgreSQL, click on the Applications card on the K10 dashboard to see the discovered PostgreSQL instance.
3. Backup and Restore Workflow using Kasten K10
In this blog, we will use K10’s default backup mechanism which relies on taking volume snapshots. Click on the Applications card in the K10 dashboard and either create a backup policy or, for experimentation, simply create a restore point to do a full manual backup.
Check the progress of the backup action in the main K10 dashboard.
Completion of the backup action will result in the creation of a restore point (a set of configuration and data artifacts) which can be used to restore from. To restore from the restore point, go to the Applications card and click on `restore` button for the `postgresql` application. Here you should see all the available restore points.
Click on the restore point. This will open the Restore panel where you can view and modify the restore parameters. Click on the Restore button to restore the associated data and specs.
Check the progress of the restore action in the main K10 dashboard.
The data and application configuration have been successfully restored.
Using Backup Policies
Note that the workflow demonstrated above used a manual backup. You can also create policies to execute backups on a scheduled basis. Policies are extremely configurable. You can set the backup schedule and snapshot retention schedule independently for fine-grained control over how often backups are performed and how much total storage they consume.
To try this out click on Create New Policy on the application card on the dashboard.
When a policy that applies to an application successfully executes a backup, the application’s compliance with the policy is reported in the application card. In the screenshot below, we can see that our postgresql application is now compliant with all policies.
Advanced Use Cases: DR and Mobility
The workflow in this blog covers snapshot, backup, and restore in a single EKS cluster. K10 can be used to export the entire application stack and its data from production clusters and restore them to a geographically separate DR cluster. You can also mask data, store it in an object store, and then read it from your local development cluster. Such use cases are described in the K10 documentation.
This blog has shared steps for backing up and restoring PostgreSQL running on AWS using snapshots as the backup mechanism. I encourage you to also explore the more advanced backup and restore approaches (based on logical dumps and database quiescing) discussed in an upcoming companion blog in this series.
In addition to backups and restores for PostgreSQL, K10 also supports backups and restores for a range of other relational databases (e.g., MySQL) and NoSQL systems (e.g., MongoDB or Elastic). I encourage you to check those out too!
Finally, we would love to hear from you to see how K10 could be useful in your Kubernetes environment. Find us on Twitter, drop us an email, or swing by our website!
Tom graduated with an M.S.E from the University of Michigan in 2013. His first job was on the server team at Maginatics, cloud based file system company which was acquired by EMC late in 2014. After the acquisition, he joined Dropbox where he was focused on improving the efficiency of Dropbox’s metadata storage, disaster recovery, and fault tolerance. In 2017, Tom joined the founding team at Kasten. Kasten is focussed on kubernetes data management, and was acquired by Veeam in 2020. He is now managing teams spanning multiple projects, all with the aim of simplifying data management in cloud-native environments.
Kasten, Inc. 8800 Lyra Drive, Suite 450 Columbus, Ohio 43240
We value the critical role that the security community plays in helping us protect the confidentiality, integrity, and availability of our software, services, and information. If you have information about security vulnerabilities that affect Kasten software, services, or information, please report it to us via our HackerOne Vulnerability Disclosure Program, or anonymously via this form.