Dynamically Calculate Timestamp Limits for Continuous Backup Restore (via OPLOG Timestamp)
Currently, you can put in a OPLOG TIMESTAMP value that exceeds the maximum / minimum value for the Continuous Backup Time Window.
For example, on the "Date & Time" tab of the "Point in Time Restore" menu, you are given a warning that specifies: "You can only restore to a specific point in time after MM/DD/YYYY HH:MM"
This should be added to the "OPLOG TIMESTAMP" tab where a warning could be given such as "You can only restore to a specific point in time after XXXXXXXXXX" (Epoch time).
As such, you should enforce data form validation so that a user cannot enter a timestamp that exceeds this minimum Epoch value. Data form validation should also be added to the "Date & Time" tab, as you are currently able to enter values into the HH:MM field such as 99:200 which are not valid Hour / Minute values.
Additionally - when the user enters an Epoch timestamp, the UI should calculate and render the correlation Human-Readable Date/Time and display a message similar to "Atlas will restore database to Friday, June 5, 2020 11:37:00 PM EST".
Lastly - UI should include help information in regards to the "increment" value, how it is used, and what the minimum / maximum values can be.
These changes will ensure there is no confusion or ambiguity on exactly when the database will be restored to.