Baron Schwartz wrote:
In contrast, InnoDB actually needs to shut down to cleanly close its table
structures before you can physically copy the filesystem.
Actually, not true -- an LVM snapshot (or other snapshot) is a great
way to take a backup of InnoDB. You just need a truly atomic
Hi Jed,
If you are using LVM, you might consider snapshotting, however, doing a live
snapshot without stopping mysql server would only work if you were copying
only myisam tables. Mysql-hot-copy would probably be better, but either way,
you need to flush your tables, which will briefly lock
Claudio,
ehmthe problems is exactly that. On production server you cannot stop or
lock the server so I need
the replication slave mainly for backups (actually MySQL replication is
simply great for this)
Just don't rely on the slave to BE the backup. You can use it to make
it easier to
All, Happy New Year, and let's hope somebody tries to stop the killing in
gaza.
I need to setup a replication slave off a master that is currently
production and not stoppable or lockable(possibly).
Do you have any idea on how to setup the slave with minimum or no impact on
the master?
The
If you're making backups of the DB, it might be possible to use the
backup data as a replication snapshot for kickstarting the slave. You
would need to be recording the master log file and position at the
time the backups are made as well, however (usually easy to hack in if
you're not already
We get asked to do this a lot :) There's a bunch of different cases.
What storage engines are you using? Do you have LVM with free space
on the volume group, or another way to take snapshots such as a SAN?
Sometimes there are clever ways to get around various limitations, but
I'll wait till you
Claudio Nanni wrote:
All, Happy New Year, and let's hope somebody tries to stop the killing in
gaza.
I need to setup a replication slave off a master that is currently
production and not stoppable or lockable(possibly).
If you are using InnoDB, there is a --single-transaction method backup
First, Thank You all guys, I really appreciate your great answers.
Second in my experience this is one of the most challenging and frequent
things with mysql on production servers,
once you have the slave practically you have online backups
I will try to answer one by one.
Jake Maul wrote:
:05 PM
To: mysql@lists.mysql.com
Subject: Setup a replication slave without stopping master
All, Happy New Year, and let's hope somebody tries to stop the killing
in
gaza.
I need to setup a replication slave off a master that is currently
production and not stoppable or lockable(possibly).
Do you
Jed Reynolds wrote:
If you are using LVM, you might consider snapshotting, however, doing
a live snapshot without stopping mysql server would only work if you
were copying only myisam tables. Mysql-hot-copy would probably be
better, but either way, you need to flush your tables, which will
Sounds like you already know the score. Yeah, we use slaves as
'backup-capable' servers too... sometimes to the point of having a
separate slave who's sole purpose in life is to be taken down and
backed up. :)
As it happens, I worked with mk-table-checksum and mk-table-sync some
today. On a ~11GB
11 matches
Mail list logo
