When you want to rekey the disks in the Cloud VM Set or you have the Auto Rekey option turned on and you want to have a new SEK key available, you need to manually generate one. When you do, KeyControl:
KeyControl does not automatically rekey any of the previously-encrypted disks. This means that, if you generate a new key and then you encrypt a disk without rekeying the other disks in the Cloud VM Set, data deduplication will not work with the newly-encrypted disk because the data blocks on the new disk will use a different offset from the data blocks on the disks using the older version of the SEK key.
After you rekey the older disks, however, data deduplication will again work for all of the disks in the Cloud VM Set.
Procedure
In the Generate New Single Encryption Key dialog box, specify the options you want to use.
|
Option |
Description |
|---|---|
| Single Key Encryption Expiration |
The date on which the SEK key will expire or "Never" if the SEK never expires. If you specify a date and the SEK key expires, access to every encrypted disk on every VM in the Cloud VM Set will be denied. What happens to the SEK key depends on the setting in the Expiration Action field. |
|
Single Key Encryption Expiration Action |
|
What to Do Next
Rekey the disks in the Cloud VM Set or make sure that Auto Rekey is enabled for the Cloud VM Set. For details, see Rekeying a Disk Using the webGUI, Rekeying a Disk using the CLI, and Configuring Auto Rekey for a Cloud VM Set.