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, Dynamic Tiering for Mainframe, active flash, and active flash for mainframe

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.

When disabling encryption, you must disable the capacity saving function settings for the virtual volume.