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

# Disaster Recovery

Taloflow maintains a proven disaster recovery capability that has been successfully tested in production environments.

### **Recovery Time Objective (RTO)**

* **Full system recovery**: Approximately 6 hours to recreate Kubernetes clusters and recover database backups from scratch
* **Typical data loss window**: Less than 1 hour in most scenarios
* **Maximum potential data loss**: Up to 24 hours (worst-case scenario)

{% hint style="success" %}
**Proven Capability**: Our recovery procedures have been successfully executed in a real production outage, demonstrating the reliability of our backup and restoration processes.
{% endhint %}

### **Redundancy Architecture**

* Service clustering eliminates single points of failure within our infrastructure
* Automated application and database restoration
* Network redundancies across multiple systems

**Emergency Failover Options**: In the event of a primary infrastructure provider outage:

* **Off-site development installation**: Provides critical access capabilities during Linode/Akamai outages
* **OVH Cloud emergency clusters**: Non-operational but available for rapid activation if needed
* These alternatives enable continued operation during extended primary infrastructure failures

**Infrastructure Dependencies**:

* **Primary hosting**: Linode (Akamai)
* **Edge services**: Cloudflare
* **Extended recovery times** may occur if these primary providers experience regional or system-wide outages
* Our multi-cloud failover strategy mitigates single-provider dependency risk


---

# 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.taloflow.ai/security/security-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.