> 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.11/onboard-cortex-xsoar/cortex-xsoar-installation/high-availability-for-cortex-xsoar.md). # High Availability for Cortex XSOAR High availability keeps your systems running even if one of your components fails. It provides redundancy for the different components, so if a problem occurs, it has a minimal effect on your system. If you deploy a cluster of three nodes and set the Cortex XSOAR IP address access to either a virtual IP or the reverse proxy/ingress controller IP, the system implements built-in high availability. This enables workload distribution and data replication across the nodes, and continuous operation in case one node fails. {% hint style="info" %} ### Note Kubernetes requires a majority of control plane nodes to be online for it to function, so a three-node cluster requires two to be online. If two nodes fail but are fixed and go back online, the cluster will recover. However, if two nodes fail and are not able to go back online, open a support session for assistance. {% endhint %} #### Built-in High Availability Built-in High Availability works as follows: * Tasks and data are distributed across the nodes to balance the load. * Data is replicated across nodes, ensuring no single point of failure. * If a node goes down, workloads on the failed node are automatically distributed to the other nodes.

Note

There may be several minutes of downtime until the other nodes take over.

* Once the failed node is restored, it automatically reintegrates into the cluster, and the workloads are automatically rescheduled. For more information on setting up built-in High Availability for your specific deployment by deploying a cluster of three nodes, see [Cortex XSOAR Installation](/cortex-xsoar-8-on-prem/8.9/onboard-cortex-xsoar/cortex-xsoar-installation.md). #### Backup and restore between primary and secondary data centers Once you deploy your cluster, you can utilize disaster recovery functionality using backup and restore operations. {% hint style="info" %} ### Important The restore environment must run the same Cortex XSOAR version with the same resources as the original environment to ensure seamless restoration (the clusters must be the same). {% endhint %} With periodic backups of the cluster to external storage, if the original cluster becomes unavailable, you can easily restore it from the external storage. For more information, see [Back up data](/cortex-xsoar-8-on-prem/8.11/onboard-cortex-xsoar/back-up-and-restore-cortex-xsoar/back-up-data.md). #### Monitor and manage nodes Once you set up and install your cluster, you can monitor node status and recover from node failure as needed. 1. In Cortex XSOAR, monitor the node health on the **System Diagnostics** page. For more information, see [View system status in the System Diagnostics page](/cortex-xsoar-8-on-prem/8.11/troubleshoot-and-reference/troubleshoot/view-system-status-in-the-system-diagnostics-page.md). 2. If there is a node failure, manage the nodes from the textual UI. For example, if a node fails remove it and then add a new node to replace it. For more information, see [Manage nodes in a cluster](/cortex-xsoar-8-on-prem/8.11/onboard-cortex-xsoar/cortex-xsoar-installation/post-installation/optimize-performance-and-robustness-from-the-textual-ui.md#UUID-0bf9620c-228e-0bdd-0477-a4b36d2d0331). You need to set the host again and reestablish trust between all the nodes if you want to replace a node in the cluster after completing the installation. --- # 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://cortex-docs.paloaltonetworks.com/cortex-xsoar-8-on-prem/8.11/onboard-cortex-xsoar/cortex-xsoar-installation/high-availability-for-cortex-xsoar.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.