12.8 Using encryption 12.8.1 Encrypted pools The design for encryption is based on the concept that a system should either be fully  encrypted or not encrypted. Encryption implementation is intended to encourage solutions  that contain only encrypted volumes or only unencrypted volumes. For example, after  encryption is enabled on the system, all new objects (for example, pools) are created by  default as encrypted. Some unsupported configurations are actively policed in code. For  example, no support exists for creating unencrypted child pools from encrypted parent pools.  However, exceptions exist: Notes:  Encryption support for Distributed RAID is available in IBM Spectrum Virtualize  V7.7 and later. You must decide whether to encrypt or not encrypt an object when it is created. You cannot  change this setting later. Volume migration is the only way to encrypt any volumes that  were created before enabling encryption on the system. For generic instructions about how to open the Create Pool window, see Chapter 6, “Storage  pools” on page 213. After encryption is enabl ed, any new pool by default is created as  encrypted, as shown in Figure 12-69. You can click  Create  to create an encrypted pool. All storage that is added to this pool is  encrypted. 688  Implementing the IBM System Storage SAN Volume Controller with IBM Spectrum Virtualize V8.2.1 Figure 12-69 Create Pool window GLYPH<SM590000> It is possible to create unencrypted arrays from CLI by manually overriding the default  encryption setting. GLYPH<SM590000> During the migration of volumes from unencrypted to encrypted volumes, a system might  report both encrypted and unencrypted volumes.