Skip to content

Commit 369eb4c

Browse files
jason-price-mongodbjason-price-mongodb
andauthored
DOCS-5801 point in time (#1095) (#1103)
* 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 6011ed0 commit 369eb4c

File tree

1 file changed

+11
-8
lines changed

1 file changed

+11
-8
lines changed

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

Lines changed: 11 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -151,14 +151,17 @@ current working directory.
151151

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

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

0 commit comments

Comments
 (0)