> For the complete documentation index, see [llms.txt](https://sirogy.gitbook.io/trellix-epolicy-orchestrator-on-prem-5.1/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sirogy.gitbook.io/trellix-epolicy-orchestrator-on-prem-5.1/disaster-recovery/module-intro.md).

# Module Intro

There are two basic ways to prepare your ePO environment for disaster recovery:&#x20;

* Disaster Recovery Snapshot Server task along with backup of the ePO database.
* Manually using detailed steps identified in [KB66616(opens in a new tab)](https://kcm.trellix.com/corporate/index?page=content\&id=KB66616).&#x20;

You can use the information in this lesson to help prepare and restore your ePO server back to a previous setting in the event of a disaster in your environment.

In this module, you will learn about how to prepare your ePO server for automated and manual disaster recovery.&#x20;

### **Module Objectives**

By the end of this module, you should be able to:

* Describe the Disaster Recovery feature and how it works
* Explain how to use a server task to take a regular Snapshot
* Take a Snapshot from the Dashboard


---

# 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:

```
GET https://sirogy.gitbook.io/trellix-epolicy-orchestrator-on-prem-5.1/disaster-recovery/module-intro.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
