Skip to content

Commit 9b819a3

Browse files
jason-price-mongodbjason-price-mongodb
andauthored
DOCS-5801 point in time (#1095) (#1106)
* DOCS-5801-point-in-time * DOCS-5801 * DOCS-5801-point-in-time * DOCS-5801-point-in-time * DOCS-5801-point-in-time Co-authored-by: jason-price-mongodb <[email protected]> Co-authored-by: jason-price-mongodb <[email protected]>
1 parent d7f9af2 commit 9b819a3

File tree

1 file changed

+16
-13
lines changed

1 file changed

+16
-13
lines changed

source/tutorial/backup-and-restore-tools.txt

Lines changed: 16 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -152,19 +152,22 @@ current working directory.
152152

153153
.. include:: /includes/fact-mongodump-overwrite-files.rst
154154

155-
Point in Time Operation Using Oplogs
156-
````````````````````````````````````
157-
158-
Use the :option:`--oplog <mongodump --oplog>` option with
159-
:binary:`~bin.mongodump` to collect the :term:`oplog` entries to build a
160-
point-in-time snapshot of a database within a replica set. With :option:`--oplog
161-
<mongodump --oplog>`, :binary:`~bin.mongodump` copies all the data from
162-
the source database as well as all of the :term:`oplog` entries from
163-
the beginning to the end of the backup procedure. This operation, in
164-
conjunction with :option:`mongorestore --oplogReplay <mongorestore --oplogReplay>`,
165-
allows you to restore a backup that reflects the specific
166-
moment in time that corresponds to when :binary:`~bin.mongodump` completed
167-
creating the dump file.
155+
Create Backups Using Oplogs
156+
```````````````````````````
157+
158+
The :option:`--oplog <mongodump.--oplog>` option with
159+
:binary:`~bin.mongodump` collects the :term:`oplog` entries and allows
160+
you to perform a backup on a live database. If you later restore the
161+
database from the backup, the database will be the same as it was when
162+
the backup process completed.
163+
164+
With :option:`--oplog <mongodump.--oplog>`, :binary:`~bin.mongodump`
165+
copies all the data from the source database as well as all of the
166+
:term:`oplog` entries from the beginning to the end of the backup
167+
procedure. This operation, in conjunction with :option:`mongorestore
168+
--oplogReplay <mongorestore.--oplogReplay>`, allows you to restore a
169+
backup that reflects the specific moment in time that corresponds to
170+
when :binary:`~bin.mongodump` completed creating the dump file.
168171

169172
.. _backup-from-non-local:
170173

0 commit comments

Comments
 (0)