> 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/restore-a-partition.md).

# Restore a Partition

Restore one or more specific Cortex XSOAR 6.15 database partitions from a backup.

Cortex XSOAR automatically backs up the database. In some cases, you might need to restore one or more partitions, without needing to restore the entire database.

{% hint style="info" %}

### Note

Any Cortex XSOAR service that uses the Elasticsearch database does not run automatic backups. To back up or restore the contents of your Elasticsearch database, follow the instructions for [Disaster Recovery for Elasticsearch](/xsoar-6-administrator-guide/6.15/onboard-cortex-xsoar/elasticsearch/disaster-recovery-for-elasticsearch.md).
{% endhint %}

1. Log out all users from Cortex XSOAR.
2. Stop the service.

   `sudo service demisto stop`
3. Back up the index directory. The default directory is `/var/lib/demisto/data/demistoidx`.

   `tar -czvf filename.tar.gz /var/lib/demisto/data/demistoidx`
4. Delete the contents of the index folder.
5. Move the `demisto_XXXXX.db` files to the partitionsData folder.
6. Set permissions.

   `sudo chown -R demisto:demisto /var/lib/demisto/data`
7. Restart the server and log in to Cortex XSOAR.

   `sudo service demisto start`

   The entire database will be reindexed, and the process might take time to complete.


---

# 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/restore-a-partition.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 `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.