PITR should restore the database as per the chunks available
Description
Tested with Everest vv0.0.0-4bc9d2a version.
Create a mongodb database. Enable the scheduled backups and PITR.
For example the latest PITR chunk creation by pbm displays the time of 13:15:36
Restore of the database From a Point-in-time (PITR) displays the time of 6:40 . If we convert 13:15:36 to the UI timezone(GMT+5.5), it comes to be 6:45:36.
If we check the UI, it displays the PITR available as per minutes and seconds
However for mongodb, the chunks are uploaded to S3 after 10 minutes, so the PITR should be displayed as per the chunks uploaded in S3.
Tested with Everest vv0.0.0-4bc9d2a version.
Create a mongodb database. Enable the scheduled backups and PITR.
For example the latest PITR chunk creation by pbm displays the time of
13:15:36Restore of the database
From a Point-in-time (PITR)displays the time of6:40. If we convert13:15:36to the UI timezone(GMT+5.5), it comes to be6:45:36.If we check the UI, it displays the PITR available as per minutes and seconds
However for mongodb, the chunks are uploaded to S3 after 10 minutes, so the PITR should be displayed as per the chunks uploaded in S3.