All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Pottage <david@electric-spoon.com>
To: Martin Steigerwald <Martin@lichtvoll.de>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Safe fsck / consistent backup while mounted
Date: Sun, 05 Jun 2011 08:58:57 +0100	[thread overview]
Message-ID: <4DEB3741.6010701@electric-spoon.com> (raw)
In-Reply-To: <201106041225.56028.Martin@lichtvoll.de>

On 04/06/11 11:25, Martin Steigerwald wrote:

> > Now I thought about a way to safely backup a MySQL or other database - 
> > without long service interruption:
> >
> > - Tell DB to turn itself into consistent state and freeze there
> > - sync / btrfs filesystem sync ; fsfreeze -f /mountpoint
> > - btrfs subvolume snapshot
> > - fsfreeze -u /mountpoint
> > - Tell DB to continue business as usual
> >
> > My questions are:
> >
> > 1) Would this work?
It should do, and it is common way to backup or check high availability
databases.

About a year ago I was responsible for a database backup and checking
system at a large blue chip company. The database was Informix, and it's
files where kept on a Netapp storage appliance, but the basic principle
was the same.

The database was frozen temporarily, a snapshot taken, and then the
database un-frozen. The snapshot was then made writable, and was then
mounted by the database engine and checked for errors. The live database
is only off line for a few seconds so the users don't notice, especaly
if the snapshot is taken at night when there are few users.

-- David Pottage


  parent reply	other threads:[~2011-06-05  7:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-04 10:25 Safe fsck / consistent backup while mounted Martin Steigerwald
2011-06-04 14:13 ` Arne Jansen
2011-06-04 16:07 ` Calvin Walton
2011-06-05  7:58 ` David Pottage [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-06-04 13:46 Tomasz Chmielewski

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=4DEB3741.6010701@electric-spoon.com \
    --to=david@electric-spoon.com \
    --cc=Martin@lichtvoll.de \
    --cc=linux-btrfs@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.