diff --git a/doc/settings/database.md b/doc/settings/database.md index f455f3a4cfdb562f1c9ede0179d65a2858adb322_ZG9jL3NldHRpbmdzL2RhdGFiYXNlLm1k..0c3d1e907b5936df86dba6958417501b1ebe7fad_ZG9jL3NldHRpbmdzL2RhdGFiYXNlLm1k 100644 --- a/doc/settings/database.md +++ b/doc/settings/database.md @@ -1166,6 +1166,9 @@ 1. Gather the replication user's password. It was set while setting up Geo in [Step 1. Configure the primary site](https://docs.gitlab.com/ee/administration/geo/setup/database.html#step-1-configure-the-primary-site). +1. Optional. [Pause replication on each **secondary** site](https://docs.gitlab.com/ee/administration/geo/index.html#pausing-and-resuming-replication) + to protect their disaster recovery (DR) capability. + 1. Manually upgrade PostgreSQL on the Geo primary. Run on the Geo primary's database node: @@ -1198,7 +1201,9 @@ `pg_hba.conf` file. This is needed because `replicate-geo-database` replicates the primary's file to the secondary. -1. Restart `puma`, `sidekiq`, and `geo-logcursor`. +1. If you paused replication in step 3, + [resume replication on each **secondary**](https://docs.gitlab.com/ee/administration/geo/index.html#pausing-and-resuming-replication). + Then, restart `puma`, `sidekiq`, and `geo-logcursor`. ```shell sudo gitlab-ctl hup puma