<!-- * Use this issue template for suggesting new docs or updates to existing docs. Note: Doc work as part of feature development is covered in the Feature Request template. * For issues related to features of the docs.gitlab.com site, see https://gitlab.com/gitlab-org/gitlab-docs/issues/ * For information about documentation content and process, see https://docs.gitlab.com/ee/development/documentation/ --> ### Problem to solve The [Bring primary back](https://docs.gitlab.com/ee/administration/geo/disaster_recovery/bring_primary_back.html) docs only refers to a deploy that contains 1 primary and 1 secondary site. It describes how to re-attach the old primary site as secondary site after a promotion. Some customers have multiple secondary sites and it is not clear what changes are needed to these sites after one of the secondary sites is promoted. For example, a deployment has the following A - Primary site B, C, D - Secondary sites Secondary site B is promoted. The old primary site A, is re-attached as a secondary site. What changes are needed to C and D to allow normal operations. ### Proposal Add detailed instruction for changes needed to secondary sites that have not been part of a promotion/failover process. These sites will need to work with the newly promoted primary. ### Who can address the issue Anyone in the Geo team. ### Other links/references <!-- E.g. related GitLab issues/MRs -->