[DOCS-5990] Comment on: "mms/tutorial/restore-replica-set.txt" Created: 06/Aug/15  Updated: 24/Feb/16  Resolved: 19/Aug/15

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Mark Helmstetter Assignee: Bob Grabar
Resolution: Done Votes: 0
Labels: collector-298ba4e7
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Location: https://docs.opsmanager.mongodb.com/current/tutorial/restore-replica-set/
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/44.0.2403.107 Safari/537.36
Referrer: https://docs.opsmanager.mongodb.com/current/search/?query=daemon%20logs
Screen Resolution: 1920 x 1200
repo: REPONAME
source: tutorial/restore-replica-set


Participants:
Days since reply: 8 years, 27 weeks, 6 days ago

 Description   

We should clarify for custom snapshots based on an oplog entry timestamp whether the specified timestamp is inclusive or exclusive. It appears that it is inclusive, i.e. the restore job will include the operation of the specified timestamp/increment.


Generated at Thu Feb 08 07:51:25 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.