> 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.12/reference-docs/reference/server-configurations/disaster-recovery-server-configurations.md).

# Disaster Recovery Server Configurations

Reference disaster recovery server configurations in Cortex XSOAR 6.12.

| Key                          | Description                                                                                                                                                                                                                                                                                                                                              | Default                 |
| ---------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------- |
| **`dr.batch.size`**          | Controls the number of actions sent to the disaster recovery server in one request. Can be used to troubleshoot live backup.                                                                                                                                                                                                                             | **`300`**               |
| **`dr.memory.limit.mb`**     | Limits the memory size (in MB) of the action items, which should prevent out of memory errors. **`dr.batch.size`** and **`dr.memory.limit.db`** work together, so the threshold is reached when the limitation of either configuration is met. If you receive an out of memory error, consider reducing to 100. Can be used to troubleshoot live backup. | **`300`**               |
| **`dr.queue.size`**          | The total number of actions to keep in memory before entering recovery mode. It is recommended to keep the default number, as it is relative to the size of the **`dr.batch.size`** configuration. Can be used to troubleshoot live backup.                                                                                                              | **`10`**\*dr.batch.size |
| **`dr.switch.http.timeout`** | Controls the HTTP timeout, in minutes of the host's request to each tenant when switching hosts.                                                                                                                                                                                                                                                         | **`5`**                 |
| **`ui.livebackup`**          | Turns on live backup. Can be used to [configure the live backup environment](/xsoar-6-administrator-guide/6.12/onboard-cortex-xsoar/disaster-recovery-and-live-backup/configure-the-live-backup-environment.md).                                                                                                                                         | **`false`**             |


---

# 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.12/reference-docs/reference/server-configurations/disaster-recovery-server-configurations.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.