Can't encrypt existing volumes?

[Jack Ingram]

So just upgraded to 2.3.9 as we were very excited about encryption at rest. After stumbling around and finding no way to turn it on for existing volumes, we visited the help docs and there it was at the bottom:

Note: Volumes that were created in Nimble versions earlier than version 2.3.x are not encrypted and cannot be edited to be encrypted. The encryption state specified when creating a volume cannot be changed for the life of that volume.

This seems incredibly short sighted by the dev team. I shouldn't need to clone full volumes or rearchitect things just to get encryption on existing volumes in production. Is this a feature that is coming or are we screwed and need to plan on dealing with migrating data to newly encrypted volumes and all of the pain that potentially entails?

[tlux131 · Accepted solution]

Jack,

The encryption at rest requires creating a new volume as you mention.  Since the encryption is at rest, there is no real way to encrypt on the fly if you will.  There aren't any current plans to change this functionality.  If you bought another SAN, usually you would specify encrypted drives up front.  In that case you would be migrating from one SAN to another.  With Nimble, we added that functionality with software.  Hope this helps.  Feel free to reach out if you need more info. 

Tony

Enterprise SE

MO, KS