> 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/2026.2/server-installation/data-center-edition/on-kubernetes-or-openshift/setting-up-disaster-recovery.md).

# Setting up disaster recovery

How to set up a disaster recovery for SonarQube Server’s Data Center Edition (DCE) deployed on Kubernetes. This page is for SonarQube Server 2026.2.

To explain the disaster recovery setup in SonarQube Server’s Data Center Edition (DCE) deployed on Kubernetes, we use the example of a system deployed on Azure Kubernetes Service (AKS). But the overall concept can be adapted to Google Cloud Platform (GCP) or Amazon Web Services (AWS) with a few modifications.

For the setup explained in this section, you need a basic understanding of Azure Cloud Services.

{% hint style="info" %}
A forced Elasticsearch reindex is required after a failover event of the Kubernetes cluster hosting the SonarQube DCE server.
{% endhint %}

{% content-ref url="/pages/ML62gMgeS42dYUHs9mMn" %}
[Disaster recovery architecture example with Azure resources](/sonarqube-server/2026.2/server-installation/data-center-edition/on-kubernetes-or-openshift/setting-up-disaster-recovery/architecture-example.md)
{% endcontent-ref %}

{% content-ref url="/pages/22tio2rhVolNLmKJLpRd" %}
[Step 1: Deploy the primary and replica databases](/sonarqube-server/2026.2/server-installation/data-center-edition/on-kubernetes-or-openshift/setting-up-disaster-recovery/deploy-databases.md)
{% endcontent-ref %}

{% content-ref url="/pages/0fW1J53P7CMGSYeqZxGm" %}
[Step 2: Set up the primary and replica clusters on AKS](/sonarqube-server/2026.2/server-installation/data-center-edition/on-kubernetes-or-openshift/setting-up-disaster-recovery/set-up-clusters-on-aks.md)
{% endcontent-ref %}

{% content-ref url="/pages/qhXMM6nrfsOMKWMojj2u" %}
[Step 3: Configure the Azure Front Door](/sonarqube-server/2026.2/server-installation/data-center-edition/on-kubernetes-or-openshift/setting-up-disaster-recovery/configure-azure-front-door.md)
{% endcontent-ref %}

{% content-ref url="/pages/otT52QIXGcUTF4wvfefl" %}
[Step 4: Test failover scenarios](/sonarqube-server/2026.2/server-installation/data-center-edition/on-kubernetes-or-openshift/setting-up-disaster-recovery/test-failover-scenarios.md)
{% endcontent-ref %}


---

# 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/2026.2/server-installation/data-center-edition/on-kubernetes-or-openshift/setting-up-disaster-recovery.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.