> ## Documentation Index
> Fetch the complete documentation index at: https://docs.leamout.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Disaster recovery

> Plan recovery around durable deployment identity and the data the current backup command protects.

A self-hosted deployment has a durable identity in `/var/lib/leamout/deployment.json`. Treat that identity, generated environment secrets, durable application state, installed license material, TLS material, and recording storage as separate recovery concerns.

The current `leamout backup` command protects deployment identity/configuration, durable application state, and installed offline license/keyring material. It does not currently include recording media or TLS certificates.

A recovery plan should therefore maintain protected copies of:

1. Leamout CLI/runtime release artifacts needed for the intended version.
2. A recent `leamout backup` archive.
3. TLS certificate/private-key material and any carrier CA bundles.
4. Recording storage when recordings must survive host loss.

After restoration, run `leamout doctor`, confirm service health, then validate signaling/media before admitting production traffic.