@@ -24,28 +24,14 @@ clusters.
24
24
.. tab:: FCV 4.2 or later
25
25
:tabid: fcv42
26
26
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.
40
30
41
31
.. note::
42
32
43
33
.. include:: /includes/facts/fcv-backup-considerations.rst
44
34
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
-
49
35
.. include:: /includes/facts/how-mms-takes-fcv42-encrypted-snapshots.rst
50
36
51
37
.. important::
@@ -149,7 +135,10 @@ Encrypt Your Backup Job
149
135
.. tab:: FCV 4.2 or later
150
136
:tabid: fcv42
151
137
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.
153
142
154
143
.. tab:: FCV 4.0 or earlier
155
144
:tabid: fcv40
@@ -161,4 +150,3 @@ Encrypt Your Backup Job
161
150
head databases.
162
151
163
152
.. include:: /includes/steps/enable-backup.rst
164
-
0 commit comments