> For the complete documentation index, see [llms.txt](https://docs.ionos.com/cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ionos.com/cloud/backup-and-storage/backup-service/how-tos/apply-backup-encryption.md).

# Apply Backup Encryption

By default, the <code class="expression">space.vars.backup\_service</code> uses AES-256 server-side encryption for storage devices, preventing unauthorized access outside the server. This document describes how to apply client-side AES-256 encryption to a protection plan using a password.

{% hint style="info" %}
**Prerequisites:**

* Make sure that your browser allows popups.
* Only contract administrators, owners, or users with the **Create Backup Units** privilege can manage Backup Units.
  {% endhint %}

{% stepper %}
{% step %}

## Navigate to the Backup Unit Manager

1\. In the **DCD**, go to **Menu** > **Backup & Storage** > **Backup Unit Manager**.

2\. Select the required backup unit and click **Open Console**.

![Open Backup Service Console](https://1737632334-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MifAzdGvKLDTtvJP8sm%2Fuploads%2Fgit-blob-3b4c594754872c505d2336964e4b5fe134c05528%2Fbackup-service-backup-console-menu.png?alt=media)
{% endstep %}

{% step %}

## Start a new protection plan

Backup encryption can be enabled only during creation of the new protection plan.

1\. Navigate to **MANAGEMENT** > **Protection plans**.

2\. Click **Create Plan** in the right pane.
{% endstep %}

{% step %}

## Set the encryption password

1\. Click on the **Specify password** link in the **Encryption** section.

![Enable Specify password in the Encryption section](https://1737632334-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MifAzdGvKLDTtvJP8sm%2Fuploads%2Fgit-blob-26ed2ee5ee5078a9ad79d446f100c09507f75cac%2Fbackup-service-create-protection-plan.png?alt=media)

2\. Enter a strong encryption password and confirm it to ensure there are no typos. Store this password securely, as you will need it to restore backups.
{% endstep %}

{% step %}

## Configure additional settings

1\. Configure any additional settings for your protection plan.

2\. Assign the protection plan to your devices.
{% endstep %}
{% endstepper %}

{% hint style="success" %}
**Result:** The backups are encrypted with the specified password, ensuring that the data is secure and can only be restored using this password.
{% endhint %}

{% hint style="warning" %}
**Note:** Backup agents on your devices encrypt data locally before sending it to the <code class="expression">space.vars.backup\_service</code>. If you lose your encryption password, you cannot restore your data. Store this password securely.
{% endhint %}


---

# 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.ionos.com/cloud/backup-and-storage/backup-service/how-tos/apply-backup-encryption.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.
