> 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.15/onboard-cortex-xsoar/disaster-recovery-and-live-backup/troubleshoot-live-backup.md).
# Troubleshoot Live Backup
Troubleshoot live backup and disaster recovery scenarios in Cortex XSOAR 6.15.
The following are recommendations for live backup errors.
### **Live Backup Error Message on the Disaster Recovery Page**
This message indicates the system is in Recovery Mode and how many actions remain to be transferred before it exits Recovery Mode.
If due to connectivity issues data transfer is either slow or suspended between the live backup server and the production server, actions can accumulate on the live backup server. Once connectivity is restored, the system enters Recovery Mode until the accumulated actions are transferred.
### **Out of Memory Error Message**
If you receive an out-of-memoryout of memory error when live backup is enabled, consider changing the server configurations for disaster recovery.
1. Select Settings → ABOUT → Troubleshooting → **Add Server Configuration**.
2. Add the following configurations
| Key | Description | Value |
| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------- |
| `dr.batch.size` | Controls the number of actions sent to the disaster recovery server in one request. A very high value can cause memory issues. A very low value can cause performance issues, which causes the backup server to be synced slower (not in real-time).
It is recommended to start low (25-50) and increase according to memory usage.
| Default is `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.
| Default is `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. | Default is `10*dr.batch.size` |
---
# 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 dynamically 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.15/onboard-cortex-xsoar/disaster-recovery-and-live-backup/troubleshoot-live-backup.md?ask=&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 `build a script that syncs our docs to a CMS` 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.