|
1 | 1 | 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. |
7 | 26 |
|
8 | 27 | In addition, ensure that you are using the same version of
|
9 | 28 | :binary:`~bin.mongorestore` to load the data files as the version of
|
|
0 commit comments