From: Brian Kroth <bpkroth@gmail.com>
To: Tanner Danzey <arkaniad@gmail.com>
Cc: gentoo-server@lists.gentoo.org
Subject: Re: [gentoo-server] MySQL Backup
Date: Mon, 16 Apr 2012 10:26:02 -0500 [thread overview]
Message-ID: <20120416152542.GA6809@gmail.com> (raw)
In-Reply-To: <CALPw5E42EfPKrnN2Z0HGyOYcBBKnzYgwW3=gojdGA3KNJTaq6g@mail.gmail.com>
I use this for some very large data sets as well. The trouble is that
to do it right you have to lock the tables while it's running, so I
actually run it off replication slaves instead. One of the nice things
of doing things this way is that you can use perl or your other favorite
text processing tool to parse out individual databases, tables, views,
etc. That's important in a hosting environment and usually more
difficult/costly with raw file backups.
Brian
Tanner Danzey <arkaniad@gmail.com> 2012-04-15 13:10:
> I usr MySQL's "mysqldump" and a daily cron task that zips it up and sends
> it to my NFS backup drive in dated folders. It works just fine for my
> minute data set.
>
> On Apr 15, 2012 1:04 PM, "Gerry Smith" <[1]smith.gerry@gmail.com> wrote:
>
> What's recommended for MySQL backups these days ?
> I've been using zmanda, which I found very easy to install and use,
> but it doesn't seem to be in portage anymore ?
>
> Thanks,
>
> Gerry Smith
>
> References
>
> Visible links
> 1. mailto:smith.gerry@gmail.com
next prev parent reply other threads:[~2012-04-16 15:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-15 17:56 [gentoo-server] MySQL Backup Gerry Smith
2012-04-15 17:58 ` kojiro
2012-04-15 18:10 ` Tanner Danzey
2012-04-16 15:26 ` Brian Kroth [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-04-15 19:40 Jesse Pasichnyk
[not found] <20120415194144.C6BE9E0DBB@pigeon.gentoo.org>
2012-04-15 21:51 ` Robert Bridge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120416152542.GA6809@gmail.com \
--to=bpkroth@gmail.com \
--cc=arkaniad@gmail.com \
--cc=gentoo-server@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox