Skip to content

Commit 3bc1e67

Browse files
authored
DOCSP-17316 Update mongodump/restore Behavior (#97)
* DOCSP-17316 Update mongodump/restore Behavior * * * * * IR1 * IR * * * * * IR Final
1 parent 8357829 commit 3bc1e67

File tree

1 file changed

+24
-5
lines changed

1 file changed

+24
-5
lines changed

source/includes/fact-match-dump-restore-versions.rst

Lines changed: 24 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,28 @@
11
When using :binary:`~bin.mongorestore` to load data files created by
2-
:binary:`~bin.mongodump`, be sure that you are restoring to the *same
3-
major version* of the MongoDB Server that the files were created from.
4-
For example, if your dump was created from a MongoDB Server running
5-
version ``4.4.x``, be sure that the MongoDB Server you are restoring to
6-
is also running version ``4.4.x``.
2+
:binary:`~bin.mongodump`, the MongoDB versions of your source and
3+
destination deployments must be either:
4+
5+
- The same major version.
6+
- The same feature compatibility version.
7+
8+
For example, if your dump was created from a MongoDB deployment running
9+
version ``4.4``, the MongoDB deployment you restore to must also run
10+
version ``4.4`` or have its FCV set to ``4.4``.
11+
12+
To change your feature compatibility version, see
13+
:dbcommand:`setFeatureCompatibilityVersion`.
14+
15+
.. note::
16+
17+
You can restore the BSON files generated from ``mongodump``
18+
into MongoDB deployments running the same or newer version
19+
as the source deployment.
20+
21+
This guarantee does not apply to metadata, archive, or oplog replay
22+
files. If you try to restore these files using different
23+
source and destination deployment versions, the ``mongorestore``
24+
process could result in failure, silent failure, or corrupted
25+
metadata.
726

827
In addition, ensure that you are using the same version of
928
:binary:`~bin.mongorestore` to load the data files as the version of

0 commit comments

Comments
 (0)