> For the complete documentation index, see [llms.txt](https://notebook.iuriioapps.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://notebook.iuriioapps.com/cloud/aws/high-availability/disaster-recovery.md). # Disaster recovery * **RTO - Recovery Time Objective** - is the time it takes after the disruption to restore a business process to its service level. * **RPO - Recovery Point Objective** - is the acceptable amount of data loss measured in time before the disaster occurs. ### Disaster recovery strategies * **Backup and restore** - storing backup data on S3 and recover data quickly and reliably. * **Pilot light** - for quick recovery into AWS - quicker recovery times than backup and restore, because core pieces of the system are already running and are continually kept up-to-date * **Warm standby** - a scaled-down version of a fully functional environment is always running in the cloud. * **Multi-site** - run your infrastructure on another site, in an active-active configuration. --- # 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://notebook.iuriioapps.com/cloud/aws/high-availability/disaster-recovery.md?ask=&goal= ``` `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.