WAL-G
WAL-G is a simple and efficient archival restoration tool for PostgreSQL that simplifies Continuous Archiving and Point-in-Time Recovery (PITR) and can store backups in S3, Google Cloud Storage, Azure, Swift, remote host (via SSH), or local file system.
In order to set up continuous backups, you need to do the following:
Configure wal-g
access to external storage
wal-g
access to external storageFor example. If you use GCP GCS you should configure ENV Variables
Enable archiving of logs in Postgres and specify archive command and restore_command
Make a base backup
For taking a backup you should run wal-g backup-push
inside the AidboxDb container
You can always restore the database from base backup if your database is corrupted.
To start rotating wal logs and backups schedule you can schedule retain cron job
This will delete all but 30 latest backups.
Backups integrity
WAL-G includes wal-g wal-verify
a command that checks backup integrity.
Aidboxdb recovery:
Configure WAL-G access to external storage
Download backup
wal-g
backup-pull
$PGDATA
Configure the
wal-g wal-fetch
restore commandStart Postgres
Postgres download all the missing logs and read them on start.
In replica mode Postgres operates in "read-only" mode, continues to receive WAL logs and lags minimum one WAL file behind main instance.
Incremental backups
You can configure incremental backups with env variable WALG_DELTA_MAX_STEPS
.
So the backup will be faster, but the recovery process will take longer.
What WAL-G doesn't work for?
WAL-G is not a replacement of
pg_dump
.pg_dump
is used to create a logical dump of one or several DBs in cluster.WAL-G doesn't schedule backup automatically.
Last updated