Charmed PostgreSQL VM

Channel Revision Published Runs on
latest/stable 345 09 Nov 2023
Ubuntu 22.04 Ubuntu 20.04 Ubuntu 18.04 Ubuntu 16.04
14/stable 363 21 Feb 2024
Ubuntu 22.04
14/candidate 405 03 May 2024
Ubuntu 22.04
14/beta 409 23 May 2024
Ubuntu 22.04
14/edge 409 21 May 2024
Ubuntu 22.04
juju deploy postgresql --channel 14/stable
Show information



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!


  • 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!):

  1. Retrieve root/admin level credentials from legacy charm.

    See examples here.

  2. Install pgBackRest inside the old charm OR nearby.

    Ensure the version is compatible with pgBackRest in the new Charmed PostgreSQL revision you are going to deploy! See examples here.

    Note: You can use charmed-postgresql SNAP/ROCK directly. More details here.

  3. Configure storage for database backup (local or remote, S3-based is recommended).

  4. Create a first full logical backup during the off-peak

    See an example of backup command here.

  5. Restore the foreign backup to the Charmed PostgreSQL installation in your test environment.

  6. Perform all the necessary tests to make sure your application accepted the new database.

  7. 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!

Help improve this document in the forum (guidelines). Last updated 3 months ago.