Dominic Marks wrote:
On Tuesday 03 May 2005 20:30, Danny Butroyd wrote:
Hi All
First of all I would just like to say how much I like Bacula, its a
superb bit of software, so thanks guys!
What I would like to know is what do most people do when backing up
heavily used mysql databases? Do people prefer to backup the live files
and "repair tables" if you have to restore or do people have other ways
to do it? I have toyed with the idea of backing up the databases from a
script and backing up the dump file to bacula but im not sure this is
the best way to go.
Would it not be better to use replication? If the database is large the dump
and restore may take valuable time to complete, and will not be as up to date
as a replicated database. The bacula catalogue is backed up in the way you
describe (by default anyway), if you haven't already discounted replication
for some other reason it might be the answer to your problem.
You could even combine the two, run regular dumps from the replicant into
bacula so as to reduce interuption and performance degradation of your
primary db server.
To be honest the second suggestion you have made is something I have
already thought of and for some of our more critical machines I will
actually be implementing that solution (ie second server, replication
and dumps). I just wanted to get other peoples thoughts on this issue
as i have quite a few other "less important" DBs to think about too.
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
