Ongoing physical backups with Docker & WAL-E

URL: llms-txt#ongoing-physical-backups-with-docker-&-wal-e

Contents:

• Run the TimescaleDB container in Docker
  • Running the TimescaleDB container in Docker
• Perform the backup using the WAL-E sidecar
  • Performing the backup using the WAL-E sidecar
• Recovery
  • Restoring database files from backup
  • Relaunch the recovered database

When you run TimescaleDB in a containerized environment, you can use [continuous archiving][pg archiving] with a [WAL-E][wale official] container. These containers are sometimes referred to as sidecars, because they run alongside the main container. A [WAL-E sidecar image][wale image] works with TimescaleDB as well as regular Postgres. In this section, you can set up archiving to your local filesystem with a main TimescaleDB container called timescaledb, and a WAL-E sidecar called wale. When you are ready to implement this in your production deployment, you can adapt the instructions here to do archiving against cloud providers such as AWS S3, and run it in an orchestration framework such as Kubernetes.

Tiger Cloud is a fully managed service with automatic backup and restore, high availability with replication, seamless scaling and resizing, and much more. You can try Tiger Cloud free for thirty days.