> * flush atbles
> * rsync while mysqld is running
> * stop mysqld
> * second rsync
>
Unless we can verify 100% that there is a safe way to do it without
shutting down MySQL, then I'm sure the approach you described above is
the one we will end up with. Thanks for your input.
--
Eric Robinson
Am 28.01.2011 22:30, schrieb Robinson, Eric:
> Our current model has been working well since 2006. We will be careful
> to verify the reliability of any proposed changes.
>
> Have a great day!
this is ok because MyISAM is so simple that you can even without any
flushes make a copy while the ser
> And you will build your business on a hotcopy with external
> tools beause you do not trust replication? laughable!
>
> Do what you want, but dont come back and cry if all goes down
> You were told in which way you can use rsync with minimum
> downtime or that replication can be used to stop
Am 28.01.2011 17:04, schrieb Robinson, Eric:
> Just refreshing this topic a bit. Can anyone confirm that FLUSH TABLES
> WITH READ LOCK is sufficient to quiesce the InnoBD background threads
> per Shawn's message above?
Damned start your brain, read documentations and hear what peopole say
http:
> In one extreme instance, having a few terabytes of data
> across several instances (on distinct hosts), I was required
> to do a full-refactoring data migration with an absolute
> limitation on allowable downtime.
> Among the technique which I used (and I can't take credit for this
> one) was
FLUSH TABLES WITH READ LOCK does work consistently on MyISAM and my
experience confirms this. I do remember reading something on this
list eons ago that asserted that it is not necessarily effective on
InnoDB due to it's multi-versioning.. uncommited transactions might be
caught in an inconsisten
> You need to quiesce the InnoDb background threads. One
> technique is mentioned here:
> http://dev.mysql.com/doc/refman/5.5/en/innodb-multiple-tablesp
aces.html
Just refreshing this topic a bit. Can anyone confirm that FLUSH TABLES
WITH READ LOCK is sufficient to quiesce the InnoBD background
