With today's streaming technologies applying updates to CS continuous it is not possible to just stop all streams of input while backup is running. People can have in the 100's of data streams and pausing for an update is not always possible. Must have no blocking HOT backups.

Need this asap or we may consider other solutions

Todd brought up what is likely the quickest-to-impl sol'n. We could accept a dirty initial backup, then lock for writing and do an incremental backup. It would still block writes but for a shorter duration, and we'd get a consistent snapshot. That or something similar might be acceptable in the short term.

The "create date" on this ticket is pre-convergence with MariaDB server. If the issue still exists in a modern version of the engine/plugin please submit a new ticket.