diff --git a/doc/admin-guide-cloud/blockstorage/section_volume-backups-export-import.xml b/doc/admin-guide-cloud/blockstorage/section_volume-backups-export-import.xml
index 805170d62d..fe8fe8f281 100644
--- a/doc/admin-guide-cloud/blockstorage/section_volume-backups-export-import.xml
+++ b/doc/admin-guide-cloud/blockstorage/section_volume-backups-export-import.xml
@@ -19,6 +19,11 @@
         backup, even in the event of a catastrophic database failure. This will preclude the need to
         back up the entire Block Storage database, particularly if you only need to keep complete
         backups of a small subset of volumes.</para>
+    <para>If you have placed encryption on your volumes, the encryption will still be in place when
+        you restore the volume if a UUID encryption key is specified when creating volumes. Using
+        backup metadata support, UUID keys set up for a volume (or volumes) will remain valid
+        when you restore a backed-up volume. The restored volume will remain
+        encrypted, and will be accessible with your credentials.</para>
     <para>In addition, having a volume backup and its backup metadata also provides volume
         portability. Specifically, backing up a volume and exporting its metadata will allow you to
         restore the volume on a completely different Block Storage database, or even on a different
diff --git a/doc/admin-guide-cloud/blockstorage/section_volume-backups.xml b/doc/admin-guide-cloud/blockstorage/section_volume-backups.xml
index 11a01a2763..64b2d29bed 100644
--- a/doc/admin-guide-cloud/blockstorage/section_volume-backups.xml
+++ b/doc/admin-guide-cloud/blockstorage/section_volume-backups.xml
@@ -16,6 +16,9 @@
     <para>Alternatively, you can export and save the metadata of selected volume backups. Doing so
       precludes the need to back up the entire Block Storage database. This is useful if you need
       only a small subset of volumes to survive a catastrophic database failure.</para>
+    <para>If you specify a UUID encryption key when setting up the volume specifications, the
+      backup metadata ensures that the key will remain valid when you back up and restore
+      the volume.</para>
     <para>For more information about how to export and import volume backup metadata, see <xref
         linkend="volume-backup-restore-export-import"/>.</para>
   </note>