<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Courier New";}
span.EmailStyle20
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal>Caitlin Bestler wrote:<span style='font-size:10.0pt;font-family:"Courier New"'><o:p></o:p></span></p><p class=MsoNormal>> How does encryption relate to snapshots?<o:p></o:p></p><p class=MsoNormal>> Is the snapshot encrypted with the same key as the volume? <o:p></o:p></p><p class=MsoNormal>> Not doing so would force snapshot creation to be a very time consuming <o:p></o:p></p><p class=MsoNormal>> operation. The most efficient snapshots are ZFS style where the current <o:p></o:p></p><p class=MsoNormal>> blocks are just frozen, which would mean they are still encrypted. <o:p></o:p></p><p class=MsoNormal>> Accessing the snapshot requires access to the key that the volume used. <o:p></o:p></p><p class=MsoNormal>> How will this be tracked? <o:p></o:p></p><p class=MsoNormal>Taking a snapshot of a volume will require associating the encryption key(s) used by the original volume with the snapshot.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>> How do we prevent the key from being deleted while there are snapshots that<o:p></o:p></p><p class=MsoNormal>> still rely on it?<o:p></o:p></p><p class=MsoNormal>Making a copy of the encryption key(s) of the original volume avoids the possibility of deleting keys required by a snapshot.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>> Is this compatible with thin provisioning of clone copies (especially for<o:p></o:p></p><p class=MsoNormal>> local volumes)? Is a thinly provisioned clone copy required to use the<o:p></o:p></p><p class=MsoNormal>> same key as the snapshot it was based upon?<o:p></o:p></p><p class=MsoNormal>The clone would be required to use the same key. If there is a requirement for a local copy using a separate key, this would be considered, but this would double the encryption processing performance penalty.<o:p></o:p></p></div></body></html>