Supported storage types
You can enable CryptoHub encryption for the following storage types:| Storage type | Encryption scope |
|---|---|
| Capacity tier (scale-out backup repository) | All backup data offloaded to object storage |
| Archive tier (scale-out backup repository) | All backup data moved to archive storage |
| Tape media pools | All backup data written to tape |
| GFS tape media pools | All backup data written to tape using GFS retention |
| Backup repositories for Veeam Plug-in for Nutanix AHV | All backups stored by the plug-in |
| Backup repositories for Veeam Backup for OLVM and RHV | All backups stored by the solution |
| Backup repositories for Veeam Kasten | All backups stored by Kasten |
| Backup repositories for standalone Veeam Plug-ins for Enterprise Applications | All backups stored by standalone plug-ins |
Standard backup repositories (Windows, Linux, SMB, NFS) do not support storage-level KMS encryption. Use job-level encryption for backups stored in these repositories.
Enabling encryption for capacity tier
Capacity tier extends a scale-out backup repository to cloud or S3-compatible object storage. Enabling encryption protects backup data offloaded from the performance tier.Prerequisites
Before enabling capacity tier encryption, verify:- A scale-out backup repository exists with a capacity tier configured.
- CryptoHub is registered as a KMS server in Veeam.
Procedure
In the Veeam Backup & Replication console, navigate to Backup Infrastructure > Scale-out Repositories.
All backup data offloaded to the capacity tier is encrypted using CryptoHub. Data already present in the capacity tier before enabling encryption remains unencrypted.
Encrypting existing capacity tier data
To encrypt data already present in the capacity tier, you must evacuate the data back to the performance tier, enable encryption, and then allow Veeam to offload the data again.In the scale-out backup repository settings, temporarily disable the capacity tier by clearing Extend scale-out backup repository capacity with object storage.
Wait for Veeam to evacuate data from the capacity tier to the performance tier. Monitor progress in Home > Last 24 Hours.
Edit the scale-out backup repository again and re-enable the capacity tier with encryption enabled.
Veeam offloads data to the capacity tier using the new encryption settings.
Enabling encryption for archive tier
Archive tier moves older backups to low-cost archive storage (such as AWS S3 Glacier or Azure Archive). Encryption configuration follows the same process as capacity tier.In the Veeam Backup & Replication console, navigate to Backup Infrastructure > Scale-out Repositories.
All backup data moved to the archive tier is encrypted using CryptoHub.
Enabling encryption for tape media pools
Tape encryption protects backup data written to tape media. You configure encryption at the media pool level.Creating an encrypted media pool
All data written to tapes in this media pool is encrypted using CryptoHub.
Enabling encryption for an existing media pool
Data written to tapes in this media pool after the change is encrypted. Existing tape content remains encrypted with the previous key (if any) or unencrypted.
Enabling encryption for GFS media pools
GFS (Grandfather-Father-Son) media pools use a separate configuration for long-term tape retention. The encryption procedure is similar to standard media pools.All data written to tapes in this GFS media pool is encrypted using CryptoHub.
Enabling encryption for standalone plug-in backup repositories
Backup repositories that store data from standalone Veeam plug-ins and additional solutions support storage-level encryption. This includes repositories used by:- Veeam Plug-in for Nutanix AHV
- Veeam Backup for OLVM and RHV
- Veeam Kasten for Kubernetes
- Standalone Veeam Plug-ins for Enterprise Applications (Oracle RMAN, SAP HANA, SAP on Oracle)
Procedure
In the Veeam Backup & Replication console, navigate to Backup Infrastructure > Backup Repositories.
All backup data written to this repository by supported plug-ins and solutions is encrypted using CryptoHub.

