text: **12.8 Using encryption**
  
  The design for encryption is based on the concept that a system is 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 by default created 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: 
  
  (cid:2) During the migration of volumes from unencrypted to encrypted volumes, a system might 
  report both encrypted and unencrypted volumes. 
  
  (cid:2) It is possible to create unencrypted arrays from CLI by manually overriding the default 
  encryption setting. 
  
  **Notes:**Encryption support for Distributed RAID is available in IBM Spectrum Virtualize 
  code 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. To change the encryption state of stored data, you must migrate 
  from an encrypted object (for example, pool) to an unencrypted one, or vice versa. Volume 
  migration is the only way to encrypt any volumes that were created before enabling 
  encryption on the system. 