maria-developers team mailing list archive

[Pavel Ivanov <pivanof@xxxxxxxxxx>]

On Tue, May 14, 2013 at 5:31 AM, Kristian Nielsen
<knielsen@xxxxxxxxxxxxxxx> wrote:
> Though I wonder - if you are not copying binlog files, how do you deal with
> transactions inside InnoDB that are in the prepared state when the consistent
> filesystem copy is taken? Normally, the binlog is used to recover correctly,
> by rolling back those that did not commit to the binlog, and committing those
> that do. But without the binlog on the restored server, I wonder how you
> handle this.
>
> Are you sure that you get prepared transactions rolled back/committed
> correctly inside InnoDB? And that the resulting InnoDB state matches the
> binlog position you associate with the restored backup?

We reaching consistency in the backup by shutting down the server. I
would think InnoDB state shouldn't be a problem in such situation. Am
I right?