Please analyze the feasibility to implement a way to query the oplog dumps through the PBM CLI. The reason behind this is to provide a way to accurately find which PITR timestamp we will restore. In a situation where an undesired command was issued in 24 hours, it would help and speed up disaster recovery if there is a way to faster identify the timestamp to be restored.
For example: looking for a drop command and check when was the timestamp amongst the archived (dumped) oplogs through PITR.
Environment
None
AFFECTED CS IDs
CS0019050
Smart Checklist
Activity
Akira Kurogane July 5, 2021 at 7:04 AM
Hi Pransenjeet.
This is not so technically difficult, but I don't see a need for it except for the case when you want to do a tailored restore as imagined in . Is that correct?
Please analyze the feasibility to implement a way to query the oplog dumps through the PBM CLI. The reason behind this is to provide a way to accurately find which PITR timestamp we will restore. In a situation where an undesired command was issued in 24 hours, it would help and speed up disaster recovery if there is a way to faster identify the timestamp to be restored.
For example: looking for a drop command and check when was the timestamp amongst the archived (dumped) oplogs through PITR.