Details
-
Bug
-
Resolution: Done
-
Major - P3
-
None
-
None
-
*Location*: https://docs.opsmanager.mongodb.com/current/faq/
*User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.111 Safari/537.36
*Referrer*: https://jira.mongodb.org/browse/HELP-1709
*Screen Resolution*: 1920 x 1080
*repo*: REPONAME
*source*: faq
*Location*: https://docs.opsmanager.mongodb.com/current/faq/ *User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.111 Safari/537.36 *Referrer*: https://jira.mongodb.org/browse/HELP-1709 *Screen Resolution*: 1920 x 1080 *repo*: REPONAME *source*: faq
Description
clarify that for Ops Manager the PIT window is actually configurable up to as many as 365 days back (not limited to 24-hours). "Although it is faster to provide a restore for the time at which a snapshot was actually stored, this might not be ideal when restoring a replica set or sharded cluster. In consequence, Ops Manager can build a restore to any point in time within a 24-hour period by replaying the oplog to the desired time."