Supported job types
You can enable CryptoHub encryption for the following job types:- Backup jobs
- Backup copy jobs
- Veeam Agent backup jobs (managed mode)
- Application backup policies (managed mode)
- File backup jobs
- Object storage backup jobs
- Transaction log backup jobs
- Transaction log backup copy jobs
- VeeamZIP jobs
Configuration backup jobs do not support KMS encryption. These jobs use password-based encryption only.
Enabling encryption for a new backup job
The following procedure describes how to enable CryptoHub encryption when creating a new backup job. The steps apply to VM backup jobs; other job types follow a similar workflow.Select Backup Job from the ribbon, then select the appropriate workload type (for example, Virtual machine > VMware vSphere).
Complete the job wizard steps for name, virtual machines, and storage until you reach the Storage step.
In the Password dropdown, select your CryptoHub KMS server.
The dropdown displays both password-based encryption keys and KMS servers. KMS servers appear by their configured description (for example,
CryptoHub Production - Data Center 1).If you have not previously configured password loss protection and have a Veeam Backup Enterprise Manager connection, Veeam displays a Loss protection disabled warning. Select Manage passwords to configure password loss protection, or proceed without it.
The backup job is configured to encrypt backup files using keys managed by CryptoHub. Encryption begins with the next job run.
Enabling encryption for an existing backup job
You can add CryptoHub encryption to an existing backup job. New backup files created after the change are encrypted; existing backup files in the chain remain unencrypted.Backup files created by subsequent job runs are encrypted using CryptoHub. To encrypt the entire backup chain, create an active full backup after enabling encryption.
Creating an encrypted active full backup
After enabling encryption on an existing job, the next incremental backup is encrypted, but earlier restore points remain unencrypted. To create a fully encrypted backup chain, run an active full backup.Veeam creates a new full backup file encrypted with CryptoHub. Subsequent incremental backups chain to this encrypted full backup.
Enabling encryption for backup copy jobs
Backup copy jobs can use different encryption settings than the source backup job. This allows you to encrypt secondary copies even if the primary backup is unencrypted.Backup copies created by this job are encrypted independently of the source backup encryption settings.
Enabling encryption for VeeamZIP jobs
VeeamZIP creates ad-hoc full backups of individual VMs. You can enable CryptoHub encryption when creating a VeeamZIP backup.In the Veeam Backup & Replication console, navigate to Inventory and select the virtualization platform (for example, VMware vSphere).
Veeam creates an encrypted VeeamZIP backup file using CryptoHub.
Changing encryption settings
You can change the encryption key for a backup job at any time. The new key applies to backup files created after the change.Switching KMS servers
Disabling encryption
Existing encrypted backup files remain encrypted. Only new backup files are created without encryption.

