> For the complete documentation index, see [llms.txt](https://docs.sonarsource.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sonarsource.com/sonarqube-server/2025.6/server-update-and-maintenance/data-center-edition/updating.md).

# Updating

Updating your Data Center Edition. This page is for SonarQube Server 2025.6.

To update your Data Center Edition to a newer version:

1. [Determining the update path](/sonarqube-server/2025.6/server-update-and-maintenance/update/determine-path.md).
2. Read the [Release notes](/sonarqube-server/2025.6/server-update-and-maintenance/release-notes.md) between the SonarQube Server versions.
3. Back up the SonarQube Server database.
4. [Starting and stopping cluster](/sonarqube-server/2025.6/server-installation/data-center-edition/starting-stopping-cluster.md).
5. Update each application and search node as follows (do not trigger the setup phase):
   * [Pre-update steps](/sonarqube-server/2025.6/server-update-and-maintenance/update/pre-update-steps.md).
   * [Performing the update](/sonarqube-server/2025.6/server-update-and-maintenance/update/update.md).
   * [Post-update steps](/sonarqube-server/2025.6/server-update-and-maintenance/update/post-update-steps.md).
6. Once all nodes have the same binaries, restart the cluster. See [Starting and stopping cluster](/sonarqube-server/2025.6/server-installation/data-center-edition/starting-stopping-cluster.md) for more information.
7. At this point, only one of the application nodes is up and waiting for the /setup endpoint to be accessed. Try to access `node_ip:port/setup` on each application node, and trigger the setup operation on the one that responds.

## Related pages <a href="#related-pages" id="related-pages"></a>

* [DCE topology](/sonarqube-server/2025.6/server-installation/data-center-edition/dce-topology.md)
* [Starting and stopping cluster](/sonarqube-server/2025.6/server-installation/data-center-edition/starting-stopping-cluster.md)
* [Monitoring](/sonarqube-server/2025.6/server-update-and-maintenance/data-center-edition/monitoring.md) your cluster
* [Improving performance](/sonarqube-server/2025.6/server-update-and-maintenance/data-center-edition/improving-performance.md) of your cluster
* [Scaling](/sonarqube-server/2025.6/server-update-and-maintenance/data-center-edition/scaling.md) your cluster


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sonarsource.com/sonarqube-server/2025.6/server-update-and-maintenance/data-center-edition/updating.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.