The discussion revolves around the backup and restore process for a Discourse instance using an external PostgreSQL database. mreach outlines a manual backup and restore procedure using pg_dump and psql, noting that the standard Discourse backup/restore method doesn’t work due to using a newer PostgreSQL version (11). pfaffman confirms that the built-in method is supported and tested for PostgreSQL 10, but not for 11 or 12, which were later added to support gerhard and pfaffman confirm that PostgreSQL 11 and 12 are now supported. trying2survive asks about data safety during restoration, and pfaffman clarifies that only the Discourse database is affected, and the existing data remains intact if the restore fails.
I’m about to test a process of importing a boatload of content, but want to make sure I can revert properly in case things go sideways on me.
I run an external PostgreSQL instance, so my thought is that I don’t really need to backup the Discourse Rails instance in Docker, but simply the database via the following steps:
As I noted, this is for an external PGSQL database since I’m not using the Dockerized one and sadly the normal backup/restore method just doesn’t work for me (probably because I’m running a little bit newer version of PGSQL on the big DB server).
Thanks! Just to clarify, would restoring a backup to a Discourse site (with contents) completely delete all data from the external PostgreSQL database instance (RDS)? If the restoration fails or get disconnected, would the RDS data be corrupted?