The following table provides the interoperability requirements and considerations for Encryption License Key operations.
| Functions | Interoperability requirements and considerations |
|---|---|
| ShadowImage, TrueCopy, Compatible FlashCopy® V2, Compatible XRC | If the primary volume (P-VOL) of a pair (source volume for FlashCopy®) is encrypted, encrypt the secondary volume (S-VOL) (target volume for FlashCopy®) to ensure data security. |
| Thin Image | Match the encryption states of the P-VOL and pool-VOL. If the P-VOL is encrypted, encrypt all of the pool-VOLs. If the data pool contains an unencrypted pool-VOL, the differential data of the P-VOL is not encrypted. In this case, the security of the data in the S-VOL cannot be guaranteed. |
| Universal Replicator | Match the encryption states of a P-VOL and S-VOL. If you encrypt the P-VOL only, the data copied on the S-VOL is not encrypted and therefore not protected. When you encrypt a P-VOL or S-VOL, use a journal to which only encrypted LDEVs are registered as journal volumes. If the encryption states of the P-VOL, S-VOL, and journal volumes do not match, the journal data in the P-VOL is not encrypted, and the security of the data cannot be guaranteed. |
| Dynamic Provisioning, Dynamic Tiering, active flash | When enabling encryption for data written to a data pool through a V-VOL, use a data pool that consists of encrypted pool volumes. However, if the data in virtual volumes being used is encrypted, you need to perform formatting for the virtual volumes. |
| Volume Migration | Encrypt the source LDEV and the target LDEV. The encryption states of the source and target LDEVs must match for the Encryption License Key feature to encrypt and guarantee the security of the data on the source and target LDEVs. |
| Dedupe and compression | When enabling encryption, perform encryption formatting on pool volumes and virtual volumes. If a deduplication system data volume exists, make sure to initialize duplicate data. |