Interoperability requirements and considerations
The following table provides the interoperability requirements and considerations for Encryption License Key operations.
|
Functions |
Interoperability requirements and considerations |
|
ShadowImage, TrueCopy, Compatible FlashCopy® V2, and Compatible XRC |
Encrypt both the P-VOL and S-VOLs (S-VOL and T-VOLs for Compatible FlashCopy® V2) of pairs 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. |
|
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, Dynamic Provisioning for Mainframe, and Dynamic Tiering for Mainframe |
When enabling encryption for data written to a data pool with a V-VOL, use a data pool that consists of encrypted volumes. |
