> For the complete documentation index, see [llms.txt](https://help.readymage.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.readymage.com/application-management/backups/disaster-recovery-process.md).

# Disaster recovery process

Restoring an instance is a crucial undertaking that demands meticulous planning, thorough documentation, and effective communication.

It's important to acknowledge that not all incidents can be resolved by strictly adhering to predefined guides, as their nature may vary across instances.

Consequently, this guide serves as a brief overview of general steps, recognizing the need for adaptability and thoughtful consideration in addressing unique challenges that may arise during the recovery process.

1. **Assessment and Identification:**
   * Identify the nature and extent of the issue.
   * Assess the impact on users, data, and operations.
2. **Communication**
   * Reach out to <admin@readymage.com> for an assistance describing issue.
3. **Understanding scope of required recovery**
   * Identification of critical systems, prioritization of restoration steps, and roles and responsibilities for team members during a recovery scenario.
4. **Backup Verification:**
   * Verify the availability and integrity of recent backups.
   * Confirm that backups include necessary data, configurations, and settings.
5. **Recovery Plan Activation:**
   * Refer to the instance recovery plan and follow the documented steps.
   * Prioritize recovery tasks based on criticality.
6. **Data Restoration:**
   * Restore data from the most recent backup.
7. **Configuration and Settings:**
   * Reconfigure settings and configurations based on the documented standards.
   * Validate that security configurations are in place.
8. **Testing**
   * Conduct functional and performance tests to ensure the instance operates as expected.
   * Verify data integrity and consistency.


---

# 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://help.readymage.com/application-management/backups/disaster-recovery-process.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.
