A statement omission recovery allows you to search and sort the statements from the binlogs you selected. You can flag any statements you'd like to omit from the patch you would like to replay on your database.
This type of recovery is incredibly helpful if a destructive statement, such as a DROP or DELETE, was ran on your database either by accident, through an application bug, or perhaps malicious intent.
This recovery method will create a patch containing all statements in the binlogs you selected, minus any statements you selected for omission.
In some situations you may want to execute a recovery up to a certain time and disregard any statements after that. Perhaps that time is associated with the occurrence of a critical event etc. Ottomatik allows you to execute a Point In Time recovery with granularity up to the second. Additionally you can have full visibility into the statements that are associated with that particular time.
The internals of MySQL’s binary logging system keeps track of statements in a log with a "log position". Each statement has a distinct and unique start and end position. There are some advanced use-cases, often involving database replication, where you may know a particular binlog position you'd want to restore to. This functionality is similar to a Point In Time recovery, and only takes a couple clicks.