Description
https://docs.opsmanager.mongodb.com/current/tutorial/restore-replica-set/#set-the-restore-point-to-the-restore-timestamp-value-from-the-restoreinfo-file
In the above page, we want the customer to take note of the "Restore Timestamp" value in the restoreInfo.txt. This Restore Timestamp is computed with respect to the MongoDB version of when the snapshot was taken. So, if we have a customer who is attempting to restore a Snapshot which was taken on MongoDB 4.2, but when they're performing these manual restore steps, the mongod binary they're using is MongoDB 4.4, the restored data may contain unnecessary oplog documents, which can be an issue if the customer is performing PIT restores.
Note that this only occurs in this scenario of Snapshot was taken on 4.2, but the restoring binary is on 4.4. In future version (eg Snapshot on 4.4, binary on 4.6), this wouldn't occur.
We would like to add a small note in the above link (as well as the Cloud Manager Equivalent) that if a customer has a mismatch in versions, they should decrement the restore timestamp by 1, or that they should stick to using the same mongodb version.
Marking this ticket as a "Minor", since we don't expect customers to perform Manual Restores, but also because this only occurs when a customer performs a Manual Restore with a different MongoDB version than that of the Snapshot's.
Scope of changes
Impact to Other Docs
MVP (Work and Date)
Resources (Scope or Design Docs, Invision, etc.)
|