public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Skretvedt <andrew.skretvedt@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Incremental backup for a raid1
Date: Thu, 13 Mar 2014 14:48:55 -0500	[thread overview]
Message-ID: <53220BA7.1060702@gmail.com> (raw)
In-Reply-To: <20140313192832.GE6151@carfax.org.uk>

On 2014-Mar-13 14:28, Hugo Mills wrote:
> On Thu, Mar 13, 2014 at 08:12:44PM +0100, Michael Schuerig wrote:
>>
>> My backup use case is different from the what has been recently
>> discussed in another thread. I'm trying to guard against hardware
>> failure and other causes of destruction.
>>
>> I have a btrfs raid1 filesystem spread over two disks. I want to backup
>> this filesystem regularly and efficiently to an external disk (same
>> model as the ones in the raid) in such a way that
>>
>> * when one disk in the raid fails, I can substitute the backup and
>> rebalancing from the surviving disk to the substitute only applies the
>> missing changes.
>>
>> * when the entire raid fails, I can re-build a new one from the backup.
>>
>> The filesystem is mounted at its root and has several nested subvolumes
>> and snapshots (in a .snapshots subdir on each subvol).
>>
>> Is it possible to do what I'm looking for?
>
>     For point 2, yes. (Add new disk, balance -oconvert from single to
> raid1).
>
>     For point 1, not really. It's a different filesystem, so it'll have
> a different UUID. You *might* be able to get away with rsync of one of
> the block devices in the array to the backup block device, but you'd
> have to unmount the FS (or halt all writes to it) for the period of
> the rsync to ensure a consistent image, and the rsync would have to
> read all the data in the device being synced to work out what to send.
> Probably not what you want.
>
>     Hugo.
>
I'm new; btrfs noob; completely unqualified to write intelligently on 
this topic, nevertheless:
I understand your setup to be btrfs RAID1 with /dev/A /dev/B, and a 
backup device someplace /dev/C

Could you, at the time you wanted to backup the filesystem:
1) in the filesystem, break RAID1: /dev/A /dev/B <-- remove /dev/B
2) reestablish RAID1 to the backup device: /dev/A /dev/C <-- added
3) balance to effect the backup (i.e. rebuilding the RAID1 onto /dev/C)
4) break/reconnect the original devices: remove /dev/C; re-add /dev/B to 
the fs

I think this could be done online. Any one device [ABC] surviving is 
sufficient to rebuild a RAID1 of the filesystem, or be accessed alone in 
degraded fashion for disaster recovery purposes.

I think that would address point 1. Is my thinking horrible on this? 
(again, noob to btrfs)

  reply	other threads:[~2014-03-13 19:51 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-13 19:12 Incremental backup for a raid1 Michael Schuerig
2014-03-13 19:28 ` Hugo Mills
2014-03-13 19:48   ` Andrew Skretvedt [this message]
2014-03-13 21:09     ` Brendan Hide
2014-03-13 21:14     ` Michael Schuerig
2014-03-13 22:04       ` Chris Murphy
2014-03-13 23:03         ` Michael Schuerig
2014-03-14  0:29           ` George Mitchell
2014-03-14  1:14             ` Lists
2014-03-14  3:37               ` Chris Murphy
2014-03-15 11:35             ` Michael Schuerig
2014-03-15 11:53               ` Hugo Mills
2014-03-15 16:01               ` George Mitchell
2014-03-14  6:42 ` Duncan
2014-03-14  8:56   ` Michael Schuerig
2014-03-14 11:24     ` Duncan
2014-03-14 13:46       ` George Mitchell
2014-03-14 14:36         ` Duncan
2014-03-14 14:44         ` Austin S Hemmelgarn

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=53220BA7.1060702@gmail.com \
    --to=andrew.skretvedt@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox