> For the complete documentation index, see [llms.txt](https://docs.subsalt.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.subsalt.io/administration/disaster-recovery.md).

# Disaster recovery

Subsalt's system supports comprehensive disaster recovery strategies for restoring availability and data in the event of an unexpected outage or data loss/corruption.

#### Data replication

Subsalt leverages your cloud provider's block storage solution(s) for persisting data, which often have built-in resilience options available.

#### Automated back-ups

Subsalt supports each cloud provider's recommended automated Kubernetes backup solution to protect against scenarios where entire clusters are destroyed. These managed solutions provide automated, periodic backups of persistent storage to an out-of-cluster location that can be restored as needed. Recommended back-up solutions include:

* [Backup for GKE](https://cloud.google.com/kubernetes-engine/docs/add-on/backup-for-gke/concepts/backup-for-gke) on Google Cloud
* [Azure Kubernetes Service Backup](https://learn.microsoft.com/en-us/azure/backup/azure-kubernetes-service-backup-overview) on Azure
* [EKS Backup using Velero](https://aws.amazon.com/blogs/containers/backup-and-restore-your-amazon-eks-cluster-resources-using-velero/) on AWS

Third-party tools like [backy2](https://backy2.com/), [restic](https://restic.net/), and [Velero](https://velero.io/) that support filesystem-level backups are compatible with Subsalt installations as well.

#### Velero

For AKS deployments, Subsalt also supports [Velero](https://velero.io/) for backup and restore. Velero captures Kubernetes resources and persistent volume data, storing them in Azure Blob Storage. It authenticates using Azure Workload Identity, eliminating the need for static credentials in the cluster.

See the Velero backup and restore page for setup and usage details.


---

# 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://docs.subsalt.io/administration/disaster-recovery.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.
