@@ -24,28 +24,14 @@ clusters.
2424 .. tab:: FCV 4.2 or later
2525 :tabid: fcv42
2626
27- |mms| can encrypt any backup job that it had stored in a
28- snapshot store. The snapshot must come from a database that
29- ran
30- :product:`MongoDB Enterprise <mongodb-enterprise-advanced>`
31- 4.2 or later with:
32-
33- - |fcv-link| of 4.2 or later and
34- - :ref:`WiredTiger <encrypted-storage-engine>` storage engine.
35-
36-
37- .. warning::
38-
39- .. include:: /includes/facts/fcv-transitioning-from-keyfile-to-KMIP-considerations.rst
27+ |mms| doesn't encrypt backup snapshots for clusters running
28+ MongoDB 4.2 or later because you can create encrypted snapshots
29+ only from encrypted clusters.
4030
4131 .. note::
4232
4333 .. include:: /includes/facts/fcv-backup-considerations.rst
4434
45- To encrypt backups, use a master key that a |kmip|-compliant
46- key management appliance generates and maintains. This master
47- key encrypts key that encrypts the database.
48-
4935 .. include:: /includes/facts/how-mms-takes-fcv42-encrypted-snapshots.rst
5036
5137 .. important::
@@ -149,7 +135,10 @@ Encrypt Your Backup Job
149135 .. tab:: FCV 4.2 or later
150136 :tabid: fcv42
151137
152- .. include:: /includes/steps/enable-encryption-fcv42.rst
138+ You can create encrypted snapshots only from encrypted clusters.
139+ If you enable MongoDB Encryption at Rest for the host you are
140+ backing up, the bytes that |mms| copies to the snapshot
141+ store are already encrypted.
153142
154143 .. tab:: FCV 4.0 or earlier
155144 :tabid: fcv40
@@ -161,4 +150,3 @@ Encrypt Your Backup Job
161150 head databases.
162151
163152 .. include:: /includes/steps/enable-backup.rst
164-
0 commit comments