quoting Alan Williamson [EMAIL PROTECTED] ..
This recipe is intended to minimize the impact on ongoing database
operations by inhibiting writes only during a relatively speedy
operation (creating a snapshot). The long dump operation can ...
This seems to be a rather long winded way of doing
This recipe is intended to minimize the impact on ongoing database
operations by inhibiting writes only during a relatively speedy
operation (creating a snapshot). The long dump operation can ...
This seems to be a rather long winded way of doing this. Why not
replicate the database and
This recipe is intended to minimize the impact on ongoing database
operations by inhibiting writes only during a relatively speedy
operation (creating a snapshot). The long dump operation can then be
performed on the (stable) snapshot, without interfering with ongoing use
of the live database.
Hello.
A few months ago you've been writing about issues with InnoDB
when using a similar recipe. Please, share your experience of
how you've solved that problems.
James G. Sack (jim) [EMAIL PROTECTED] wrote:
This recipe is intended to minimize the impact on ongoing database
