> For the complete documentation index, see [llms.txt](https://docs.storware.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.storware.eu/backup-and-recovery-7.4/administration/virtual-environments/recovery-plans.md). # Recovery Plans Recovery plans are used to automate DR process so that Storware Backup & Recovery executes multiple restore operations to the target environment with preconfigured settings. Recovery plans can be executed on-demand or on a scheduled basis (for instance to test the recovery process periodically). Recovery plans consist of rules, each one for a particular virtualization platform, which specify VMs, restore settings, and optionally schedules. Only rules marked as active are executed. Restore operations will be performed according to the restore/import task limits set in Node Configuration. In the target environment, new VMs will be created. Names are generated by default (with optional prefix/suffix), optionally the original name can be used. For periodic restores, it is common to replace the previous VM, which typically means that options to use the original VM name and deletion of the virtual environment with the same name are checked. --- # 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.storware.eu/backup-and-recovery-7.4/administration/virtual-environments/recovery-plans.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.