Skip to content

Commit 373fbd4

Browse files
author
Sam Kleinman
committed
minor: adding link target and style correction
1 parent 14f075d commit 373fbd4

File tree

1 file changed

+11
-7
lines changed

1 file changed

+11
-7
lines changed

source/administration/backups.txt

Lines changed: 11 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -360,16 +360,18 @@ member`).
360360

361361
.. note::
362362

363-
Version 1.9.0 added :method:`db.fsyncLock()` and
364-
:method:`db.fsyncUnlock()` helpers to the :program:`mongo` shell.
365-
Prior to this version, use the following commands:
363+
..versionchanged:: 2.0
364+
In 2.0 added :method:`db.fsyncLock()` and
365+
:method:`db.fsyncUnlock()` helpers to the :program:`mongo`
366+
shell. Prior to this version, use the :dbcommand:`fsync`
367+
command with the ``lock`` option, as follows:
366368

367369
.. code-block:: javascript
368370

369371
db.runCommand( { fsync: 1, lock: true } );
370372
db.runCommand( { fsync: 1, lock: false } );
371373

372-
.. include:: /includes/note-disable-profiling-fsynclock.rst
374+
.. include:: /includes/note-disable-profiling-fsynclock.rst
373375

374376
.. _backup-amazon-software-raid:
375377

@@ -555,6 +557,8 @@ challenges for creating backups. This section describes how to make
555557
quality backups in environments with these configurations and how to
556558
perform restorations.
557559

560+
.. _sharded-cluster-backups:
561+
558562
Back Up Sharded Clusters
559563
~~~~~~~~~~~~~~~~~~~~~~~~
560564

@@ -590,8 +594,8 @@ is true:
590594
collection, the output will contain both the collection data and the
591595
sharding config metadata from the :ref:`config servers <sharding-config-server>`.
592596

593-
The :program:`mongodump` :option:`--oplog <mongodump --oplog>` option
594-
cannot be used when dumping from a mongos. This option is only
597+
You cannot use the :option:`--oplog <mongodump --oplog>` option for
598+
:program:`mongodump` when dumping from a :program:`mongos`. This option is only
595599
available when running directly against a :term:`replica set` member.
596600

597601
Back Up from All Database Instances
@@ -647,7 +651,7 @@ This procedure describes both approaches:
647651
:term:`secondary` nodes. See: :ref:`mongodump feature
648652
<mongodump-behavior>` for more information.
649653

650-
#. Back up each shard. Shards can be backed up one at a time or in
654+
#. Back up each shard. You may back up shards one at a time or in
651655
parallel. For each shard, do one of the following:
652656

653657
- If your system has disk level snapshot capabilities, create a

0 commit comments

Comments
 (0)