SERVER-6961 DOCS-455 mongodump and mongorestore documentation

Author: Bob Grabar

source/administration/backups.txt

@@ -426,6 +426,8 @@ the local database instance (e.g. ``127.0.0.1`` or ``localhost``) and
 create a database backup in a in the current directory named
 ``dump/``.
 
+.. include:: /includes/note-mongodump-compatibility-2.2.rst
+
 You can specify  database and collection as options to the
 :program:`mongodump` command to limit the amount of data included in the
 database dump. For example:

source/includes/note-mongodump-compatibility-2.2.rst

@@ -0,0 +1,5 @@
+.. note::
+
+   If you use the :program:`mongodump` tool from the 2.2 distribution to
+   create a dump of a database, you can restore that dump only to a 2.2
+   database.

source/reference/mongodump.txt

@@ -15,6 +15,8 @@ effective :doc:`backup strategy </administration/backups>`. Use in
 conjunction with :program:`mongorestore` to provide restore
 functionality.
 
+.. include:: /includes/note-mongodump-compatibility-2.2.rst
+
 .. seealso:: ":program:`mongorestore`" and ":doc:`/administration/backups`".
 
 Options

source/reference/mongorestore.txt

@@ -9,9 +9,21 @@
 Synopsis
 --------
 
-The :program:`mongorestore` utility provides the ability to import content
-from binary database dump into a specific database. This is the
-inverse functionality of :program:`mongodump`.
+The :program:`mongorestore` tool imports content from binary database
+dump into a specific database. :program:`mongorestore` can import
+content to an existing database or create a new one.
+
+Specifically, :program:`mongorestore` takes the output from
+:program:`mongodump` and restores it. :program:`mongorestore` creates
+indexes on a restore. :program:`mongorestore` performs only inserts. If
+existing data with the same ``_id`` already exists on the database,
+:program:`mongorestore` will not replace it.
+
+The :program:`mongorestore` tool does "fire-n-forget" writes. This means
+that any errors that might happen during inserts are recorded only on
+the server logs and not reported in the tool.
+
+.. include:: /includes/note-mongodump-compatibility-2.2.rst
 
 Options
 -------
@@ -32,7 +44,7 @@ Options
 
 .. option:: --version
 
-   Returns the version of the :program:`mongorestore` utility.
+   Returns the version of the :program:`mongorestore` tool.
 
 .. option:: --host <hostname><:port>
 

source/release-notes/2.2.txt

@@ -254,24 +254,16 @@ running as upserts will only output a ``null`` value.
 Previously, in version 2.0 these operations would return an empty
 document, e.g. ``{ }``.
 
-See: :issue:`SERVER-6226`.
+See: :issue:`SERVER-6226` for more information.
 
-A Version-2.2 ``mongodump`` Cannot be Restored to a Pre-2.2 Database
-````````````````````````````````````````````````````````````````````
-
-A :program:`mongodump` performed in version 2.2 cannot be imported to
-previous versions as doing so results lost indexes. If you are running
-an earlier-version database (for example a version-2.0 database), you
-cannot perform a :program:`mongorestore` on data from a version 2.2
-:program:`mongodump`.
+``mongodump`` Can Restore Only to a 2.2 Database
+````````````````````````````````````````````````
 
-In version 2.2, :program:`mongodump` does not create a
-system.indexes.bson for each database. The pre-2.2
-:program:`mongorestore` will not retain indexes that existed in the
-dumped database.
+If you use the :program:`mongodump` tool from the 2.2 distribution to
+create a dump of a database, you may only restore that dump to a 2.2
+database.
 
-.. Do we want to include a link to the ticket?
-.. See: :issue:`SERVER-6961`.
+See: :issue:`SERVER-6961` for more information.
 
 Behavioral Changes
 ~~~~~~~~~~~~~~~~~~