if i u have LVM's then lock is held only for the duration of taking
snapshot, which would be few min, if there is very less activity on the db.
On Wed, Aug 28, 2013 at 3:08 PM, Ed L. wrote:
> On 8/28/13 2:00 PM, Ananda Kumar wrote:
>
>
> Why don't u try snapshot backups, where the lock held fo
On 8/28/13 2:00 PM, Ananda Kumar wrote:
Why don't u try snapshot backups, where the lock held for less
duration. Or can't u take mysql dumps during Night time when there is
less bd activity
I neglected to mention these systems are both CentOS linux systems.
Unfortunately, the 5.5 hour dumps
Why don't u try snapshot backups, where the lock held for less duration. Or
can't u take mysql dumps during Night time when there is less bd activity
On Thursday, August 29, 2013, Ed L. wrote:
>
> Mysql newbie here, looking for some help configuring 5.0.45 master-slave
replication. Here's my sce
Mysql newbie here, looking for some help configuring 5.0.45 master-slave
replication. Here's my scenario...
We have a heavily loaded 30gb 5.0.45 DB we need to replicate via
master-slave configuration to a new, beefier server running same mysql
5.0.45, and then cutover to the new server. Du
Hi,
I have managed to get the dB open with
[mysqld]
innodb_force_recovery = 2
I did a mysqldump for all tables, and restarted with innodb_force_recordy
but still have the same old error messages.
Regards, S
On Wed, Aug 28, 2013 at 12:12 PM, Simon Loewenthal <
simon.loewent...@gmail.com> wrote
Hi there,
I just had my mysql dB crash really badly on a small server I'm running
and wonder if someone could point me in the right direction. I'm pretty
basic with mysql... I set up master/slave replication to another site, so
this could be a backup, so long as the errors were not replicated o
