> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.14/onboard-cortex-xsoar/disaster-recovery-and-live-backup/transition-between-dr-states-through-the-configuration-file.md).

# Transition Between DR States Through the Configuration File

Transition Cortex XSOAR 6.14 disaster recovery states with the configuration file during first server startup.

It is possible to transition a server between active and standby states via the `/etc/demisto.conf` configuration file, when the server is new and starts for the first time. It cannot be used at any other time.

You need to set the **`server.dr.enabled`** configuration property to **`true`** or **`false`**. If set to **`true`**, the server is in DR mode when it starts. If set to **`false`**, the server is in active mode when it starts.

`/etc/demisto.conf`

```programlisting
{  
   "Server":{  
      "HttpsPort":"443",
      "dr":{  
         "enabled":true
      }
   },
   "db":{  
      "index":{  
         "entry":{  
            "disable":true
         }
      }
   }
}
```

If the DR state of the server is ever transitioned through Cortex XSOAR, the setting is stored in the Cortex XSOAR database rather than in the `demisto.conf` file. The database config setting for **`dr.enabled`** always takes precedence over `demisto.conf`, and changing the **`server.dr.enabled`** setting in the `demistor.conf` file has no effect.

In a real disaster recovery scenario, one in which the original production server is unrecoverable, you need to convert the backup server to the new production server and then configure a new backup server.


---

# 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://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.14/onboard-cortex-xsoar/disaster-recovery-and-live-backup/transition-between-dr-states-through-the-configuration-file.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.