> For the complete documentation index, see [llms.txt](https://docs.nuvens.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nuvens.cloud/install/appendices/backup.md).

# Backup

Backups are essential for WorkSpaces Manager ensuring recovery of configuration data, policies, and operational settings in case of failure or corruption. This also provides disaster recovery.

WorkSpaces Manager (WSM) plays a vital role in automating and optimizing the lifecycle of Amazon WorkSpaces. As with any business-critical platform, ensuring a reliable backup and recovery plan is essential. In this blog post, we’ll walk through two supported deployment scenarios of WSM and how to back them up using AWS Backup. We’ll also touch on native mechanisms for Amazon RDS.

## EC2 Instance

In the All-in-One or Application-only deployment models, WorkSpaces Manager is hosted on a single EC2 instance that contains the web application, logic, and embedded database (e.g., SQL Server Express).

Why Back It Up:

* Configuration settings
* Workspace lifecycle policies
* Local SQL Express database (if not using RDS)
* Audit logs and operational metadata


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.nuvens.cloud/install/appendices/backup.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
