From 2dcabec005cc7ccb92cf451d892e0bf64fcd4aad Mon Sep 17 00:00:00 2001 From: Alex Vandiver Date: Wed, 5 Jul 2023 14:34:29 +0000 Subject: [PATCH] docs: Reference PostgreSQL version in "Restoring backups" section. This extends 8ede54fb1b7c, in the specific backups section, rather than just in the overview. (cherry picked from commit e18d0e33317f6b1290b227779863830f525305a4) --- docs/production/export-and-import.md | 16 +++++++++++++--- 1 file changed, 13 insertions(+), 3 deletions(-) diff --git a/docs/production/export-and-import.md b/docs/production/export-and-import.md index 7424bc1068..fbda961595 100644 --- a/docs/production/export-and-import.md +++ b/docs/production/export-and-import.md @@ -89,9 +89,16 @@ server's state on another machine perfectly. ### Restoring backups -First, [install a new Zulip server through Step 3][install-server] -with the same version of both the base OS and Zulip from your previous -installation. Then, run as root: +1. Install the same base OS as the backup was taken on. If you want to [upgrade + the OS][upgrade-os], you should do this after restoring the backup. + +1. [Install a new Zulip server through Step 3][install-server], with the same + version of PostgreSQL that the backup was taken on, by passing the desired + version with [the `--postgresql-version` argument][installer-options]. If + you want to [upgrade the version of PostgreSQL][upgrade-pg], you should do this after + restoring the backup. + +1. As root, import the backup: ```bash /home/zulip/deployments/current/scripts/setup/restore-backup /path/to/backup @@ -99,6 +106,9 @@ installation. Then, run as root: When that finishes, your Zulip server should be fully operational again. +[upgrade-os]: upgrade.md#upgrading-the-operating-system +[upgrade-pg]: upgrade.md#upgrading-postgresql + #### Changing the hostname It's common, when testing backup restoration, to restore backups with a