Charmed PostgreSQL VM
- By Canonical Data Platform
- Databases
| Channel | Revision | Published | Runs on |
|---|---|---|---|
| latest/stable | 345 | 09 Nov 2023 | |
| latest/stable | 239 | 09 Feb 2022 | |
| latest/stable | 226 | 01 Apr 2021 | |
| 14/stable | 468 | 11 Sep 2024 | |
| 14/stable | 467 | 11 Sep 2024 | |
| 14/candidate | 468 | 02 Sep 2024 | |
| 14/candidate | 467 | 02 Sep 2024 | |
| 14/beta | 468 | 02 Sep 2024 | |
| 14/beta | 467 | 02 Sep 2024 | |
| 14/edge | 472 | 07 Sep 2024 | |
| 14/edge | 471 | 07 Sep 2024 |
juju deploy postgresql --channel 14/stable
Deploy universal operators easily with Juju, the Universal Operator Lifecycle Manager.
Platform:
Migrate database data using ‘backup/restore’
This is a guide for migrating data from modern charms. To migrate legacy charms data, refer to the guide Migrate data via pg_dump.
This Charmed PostgreSQL operator is able to restore its ownbackups stored on S3-compatible storage. The same restore approach is applicable to restore foreign backups made by different Charmed PostgreSQL installation or even another PostgreSQL charm. The backup have to be created manually using pgBackRest!
Warning: The Canonical Data Team describes here the general approach and does NOT support nor guarantee the restoration results.
Always test a migration in a test environment before performing it in production!
Prerequisites
- Check your application compatibility with Charmed PostgreSQL VM before migrating production data from legacy charm
- Make sure PostgreSQL versions are identical before the migration
Migrate database data
Below is the general approach to the migration (see warning above!):
-
Retrieve root/admin level credentials from legacy charm.
See examples here.
-
Install pgBackRest inside the old charm OR nearby.
Ensure the version is compatible with pgBackRest in the new
Charmed PostgreSQLrevision you are going to deploy! See examples here.Note: You can use
charmed-postgresqlSNAP/ROCK directly. More details here. -
Configure storage for database backup (local or remote, S3-based is recommended).
-
Create a first full logical backup during the off-peak
See an example of backup command here.
-
Restore the foreign backup to the Charmed PostgreSQL installation in your test environment.
-
Perform all the necessary tests to make sure your application accepted the new database.
-
Schedule and perform the final production migration, re-using the last steps above.
Do you have questions? Contact us if you are interested in such a data migration!