--- stage: Enablement group: Geo info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments type: howto --- # Updating the Geo sites **(PREMIUM SELF)** WARNING: Read these sections carefully before updating your Geo sites. Not following version-specific update steps may result in unexpected downtime. If you have any specific questions, [contact Support](https://about.gitlab.com/support/#contact-support). Updating Geo sites involves performing: 1. [Version-specific update steps](version_specific_updates.md), depending on the version being updated to or from. 1. [General update steps](#general-update-steps), for all updates. ## General update steps NOTE: These general update steps are not intended for multi-site deployments, and will cause downtime. If you want to avoid downtime, consider using [zero downtime upgrades](../../../update/zero_downtime.md#multi-node--ha-deployment-with-geo). To update the Geo sites when a new GitLab version is released, update **primary** and all **secondary** sites: 1. **Optional:** [Pause replication on each **secondary** sites.](../index.md#pausing-and-resuming-replication) 1. SSH into each node of the **primary** site. 1. [Upgrade GitLab on the **primary** site](../../../update/package/index.md#upgrade-using-the-official-repositories). 1. SSH into each node of **secondary** sites. 1. [Upgrade GitLab on each **secondary** site](../../../update/package/index.md#upgrade-using-the-official-repositories). 1. If you paused replication in step 1, [resume replication on each **secondary**](../index.md#pausing-and-resuming-replication) 1. [Test](#check-status-after-updating) **primary** and **secondary** sites, and check version in each. ### Check status after updating Now that the update process is complete, you may want to check whether everything is working correctly: 1. Run the Geo Rake task on an application node for the primary and secondary sites. Everything should be green: ```shell sudo gitlab-rake gitlab:geo:check ``` 1. Check the **primary** site's Geo dashboard for any errors. 1. Test the data replication by pushing code to the **primary** site and see if it is received by **secondary** sites. If you encounter any issues, see the [Geo troubleshooting guide](troubleshooting.md).