-
Type:
Bug
-
Resolution: Done
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Labels:
-
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
*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
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.
- links to