Charmed PostgreSQL VM
- By Canonical Data Platform
- Databases
Channel | Revision | Published | Runs on |
---|---|---|---|
latest/stable | 345 | 09 Nov 2023 | |
14/stable | 363 | 21 Feb 2024 | |
14/candidate | 363 | 31 Jan 2024 | |
14/beta | 368 | 21 Feb 2024 | |
14/edge | 399 | Yesterday |
juju deploy postgresql --channel 14/stable
Deploy universal operators easily with Juju, the Universal Operator Lifecycle Manager.
Platform:
How to restore a local backup
This is a guide on how to restore a locally made backup.
To restore a backup that was made from a different cluster, (i.e. cluster migration via restore), see How to migrate cluster using backups:
Note: All commands are written for juju >= v.3.0
If you are using an earlier version, be aware that:
juju run
replacesjuju run-action --wait
injuju v.2.9
juju integrate
replacesjuju relate
andjuju add-relation
injuju v.2.9
For more information, check the Juju 3.0 Release Notes.
Prerequisites
- Deployments have been scaled-down to a single PostgreSQL unit (scale it up after the backup is restored)
- Access to S3 storage
- Configured settings for S3 storage
- Existing backups in your S3storage
List backups
To view the available backups to restore, use the command list-backups
:
juju run postgresql/leader list-backups
This should show your available backups like in the sample output below:
backups: |-
backup-id | backup-type | backup-status
----------------------------------------------------
YYYY-MM-DDTHH:MM:SSZ | physical | finished
Restore backup
To restore a backup from that list, run the restore
command and pass the corresponding backup-id
:
juju run postgresql/leader restore backup-id=YYYY-MM-DDTHH:MM:SSZ
Your restore will then be in progress.