> 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/cortex-xsoar-8-on-prem/8.10/onboard-cortex-xsoar/back-up-and-restore-cortex-xsoar.md).

# Back up and Restore Cortex XSOAR

In Cortex XSOAR 8.10 On-prem, back up and restore your cluster and data.

You can periodically back up data, configurations, and settings to ensure continuous and efficient operation of your Cortex XSOAR tenant. This minimizes downtime, prevents data loss, and helps you to recover in case of failure, corruption, or rollback.

You can perform on-demand or scheduled backups and on-demand restore from external storage.

{% hint style="info" %}

### Note

If you used backup and restore in Cortex XSOAR 8.8, consider the following;

* Your NFS server connection will be seamlessly created under Settings & Info → **Settings** → **System** → **External Storage**.
* Any existing backup schedules will be seamlessly created in the system and will continue to back up at the same scheduled times. If you see an error message that the schedule cannot be converted, contact support.
* Cortex XSOAR 8.8 backups can be viewed in the **Restore** tab by choosing the automatically created external storage, and the default relative path **`backups`**. However, restore between major versions (between 8.8 and 8.9) is not supported. To restore a Cortex XSOAR 8.8 backup, reinstall Cortex XSOAR 8.8 and restore via the CLI.
  {% endhint %}


---

# 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/cortex-xsoar-8-on-prem/8.10/onboard-cortex-xsoar/back-up-and-restore-cortex-xsoar.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.