# Disaster Recovery

{% hint style="info" %}
**Planning a disaster recovery strategy**

As of 2024.2 LTS, there is no longer a backup/restore mechanism built into the Immuta Enterprise Helm chart. Organizations are now solely responsible for creating and enacting an effective disaster recovery strategy for their installation.
{% endhint %}

All application state is stored in the PostgreSQL metadata database; therefore, recovering from a disaster event only entails restoring the aforementioned PostgreSQL database. Consult each cloud provider's point-in-time recovery (PITR) documentation for guidance:

* [Amazon RDS for PostgreSQL](https://docs.aws.amazon.com/aws-backup/latest/devguide/point-in-time-recovery.html)
* [Azure Database for PostgreSQL](https://learn.microsoft.com/en-us/azure/postgresql/flexible-server/concepts-backup-restore)
* [Google Cloud SQL for PostgreSQL](https://cloud.google.com/sql/docs/postgres/backup-recovery/pitr)

For more details about point-in-time recovery, see the [PostgreSQL documentation](https://www.postgresql.org/docs/current/continuous-archiving.html).


---

# Agent Instructions: 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:

```
GET https://documentation.immuta.com/latest/configuration/self-managed-deployment/disaster-recovery.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.