From c4d449a85816a96702a51a6bbbe4f0f7b3f7e402 Mon Sep 17 00:00:00 2001 From: Leonid Date: Fri, 23 Nov 2012 12:23:23 +0400 Subject: [PATCH] Update source/administration/backups.txt MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit  If you use :program:`mongodump` without specifying the a database or    collection, the output will contain both the collection data and the    sharding config metadata from the :ref:`config servers `. It is from version 2.2 now --- source/administration/backups.txt | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/source/administration/backups.txt b/source/administration/backups.txt index 2fba9dea752..eaa5d84b057 100644 --- a/source/administration/backups.txt +++ b/source/administration/backups.txt @@ -599,11 +599,7 @@ is true: - The backup can run and complete without affecting the performance of the cluster. -.. note:: If you use :program:`mongodump` without specifying the a database or - collection, the output will contain both the collection data and the - sharding config metadata from the :ref:`config servers `. - - You cannot use the :option:`--oplog ` option for +.. note::You cannot use the :option:`--oplog ` option for :program:`mongodump` when dumping from a :program:`mongos`. This option is only available when running directly against a :term:`replica set` member.