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

# Disaster Recovery

Recovery order:

1. Stop the container.
2. Restore `data/`.
3. Restore `.env` and secret files.
4. Restore Compose configuration.
5. Start the container.
6. Verify health.
7. Sign in and check Admin diagnostics.

Without the original secrets, encrypted integration settings and API-key validation may fail.

## Recovery Priorities

1. Preserve the current failed data directory before making changes.
2. Restore the most recent known-good backup.
3. Restore the matching `SECRET_KEY` and `MASTER_KEY`.
4. Bring up the container with the same or compatible image version.
5. Verify health and core workflows.

## Minimum Viable Recovery Test

```bash
curl --fail http://127.0.0.1:8080/api/health
```

Then verify:

* login;
* Inventory;
* Topology;
* Monitoring;
* IPAM;
* Security/syslog, if used;
* API-key authentication.

## Rollback After Failed Upgrade

Use a database backup from before the upgrade. Do not assume that a database migrated by a newer version can be safely used by an older image.

## Related Pages

* [Backups](/operations/backups.md)
* [Restores](/operations/restores.md)
* [Upgrading](/installation/upgrading.md)


---

# 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://docs.netmap.dev/operations/disaster-recovery.md?ask=<question>&goal=<endgoal>
```

`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.