---
title: "Enable or disable Encryption at Rest on a dedicated server"
description: "Find out how to enable or disable Encryption at Rest on an OVHcloud Dedicated Server from the OVHcloud Console, confirm the operation and follow its status"
url: https://docs.ovhcloud.com/en/guides/bare-metal-cloud/dedicated-servers/encryption-at-rest-enable
lang: en
lastUpdated: 2026-11-20
---
> For AI agents: the complete documentation index is available at https://docs.ovhcloud.com/en/llms.txt, the full documentation bundle is available at https://docs.ovhcloud.com/en/llms-full.txt.

# Enable or disable Encryption at Rest on a dedicated server

## Objective

Encryption at Rest encrypts all the disks of your Dedicated Server in hardware, and OVHcloud manages the passphrase that unlocks them. **This guide explains how to enable or disable Encryption at Rest from the OVHcloud Console and how to follow the operation.**

**Note:** The encryption key stays inside each disk. OVHcloud manages the passphrase that unlocks the disks, and it is never sent to you. Using your own keys is not available. For more information, read [What is Encryption at Rest on a dedicated server?](https://docs.ovhcloud.com/en/guides/bare-metal-cloud/dedicated-servers/encryption-at-rest-overview.md)

**Important:** **Enabling or disabling Encryption at Rest erases all the data on the server.** Once the operation is complete, you must reinstall the operating system. Back up your data before you start: backing it up is your responsibility.

## Requirements

- A [Dedicated Server](https://www.ovhcloud.com/en-gb/bare-metal/) on an eligible range and in an eligible region (see [Encryption at Rest requirements and limitations](https://docs.ovhcloud.com/en/guides/bare-metal-cloud/dedicated-servers/encryption-at-rest-limitations.md))
- OVHcloud Link Aggregation (OLA) not enabled on the server
- A backup of your data

***

### OVHcloud Console Access

- **Direct link:** "Dedicated servers"
- **Navigation path:** "Bare Metal Cloud" > "Dedicated servers" > Select your server

***

## Instructions

This section walks you through enabling Encryption at Rest, following the operation, and disabling it.

### Enabling Encryption at Rest

Open the `Server
` tab. The **Encryption at rest**
 line of the **Hardware**
 card shows the current state of the encryption.
1. Click "Activate Encryption at rest".
2. In the **Encryption at rest activation** window, read the warnings: operation duration, protection scope, OS reinstallation and data erasure.
3. Enter `ACTIVATE` in the confirmation field.
4. Click "Activate Encryption at rest" to start the operation.

If OLA is enabled on the server, or if the server is suspended or blocked, the activation is not available. For more details, see [Encryption at Rest requirements and limitations](https://docs.ovhcloud.com/en/guides/bare-metal-cloud/dedicated-servers/encryption-at-rest-limitations.md).

### Following the operation

The operation is asynchronous. The **Encryption at rest** line of the **Hardware** card shows its status:

| Status          | Meaning                                                                                                                     |
| --------------- | --------------------------------------------------------------------------------------------------------------------------- |
| **Inactive**    | Encryption at Rest is not enabled on the server.                                                                            |
| **In progress** | An enabling or disabling operation is running. The server restarts on its own one or more times.                            |
| **Active**      | The disks are encrypted and unlock automatically at each boot.                                                              |
| **Error**       | The operation did not succeed and the server keeps its previous state. Try again, or contact support if the error persists. |

The operation can take up to 24 hours. If a datacentre intervention is needed, the operation stays in progress until the intervention is over, which can take longer. You do not need to do anything during the operation. While it runs, other operations on the server (reinstallation, reboot, etc.) are refused.

### Reinstalling the operating system

When the operation succeeds, the server restarts in rescue mode and you receive an email. The status shows **Active** (**Inactive** after disabling). Reinstall the operating system to put the server back into service. Then restore your data from your backup.

### Disabling Encryption at Rest

Disabling Encryption at Rest cryptographically erases the disks: the data is not decrypted in place. Back up your data before you start.

On the `Server
` tab, the **Encryption at rest**
 line of the **Hardware**
 card shows **Active**
.
1. Click "Deactivate Encryption at rest".
2. In the **Encryption at rest deactivation** window, read the warnings: operation duration, server restart, end of the protection, OS reinstallation and data erasure.
3. Enter `DEACTIVATE` in the confirmation field.
4. Click "Deactivate Encryption at rest" to start the operation.

The operation takes up to 24 hours. The server restarts and stays unavailable until it comes back up. The status shows **In progress**, then **Inactive** once the operation is complete. Then reinstall the operating system.

If the status shows **Error**
 while the disks are still encrypted, the `Deactivate Encryption at rest
` button stays available: you can request the operation again.

## Go further

[What is Encryption at Rest on a dedicated server?](https://docs.ovhcloud.com/en/guides/bare-metal-cloud/dedicated-servers/encryption-at-rest-overview.md)

[Manage Encryption at Rest on a dedicated server with the API](https://docs.ovhcloud.com/en/guides/bare-metal-cloud/dedicated-servers/encryption-at-rest-api.md)

[Encryption at Rest on dedicated servers: FAQ](https://docs.ovhcloud.com/en/guides/bare-metal-cloud/dedicated-servers/encryption-at-rest-faq.md)

Join our [community of users](https://community.ovhcloud.com/).
