public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Schuerig <michael.lists@schuerig.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: Incremental backup for a raid1
Date: Sat, 15 Mar 2014 12:35:30 +0100	[thread overview]
Message-ID: <1789445.UA8sCrE2Cn@fuchsia> (raw)
In-Reply-To: <53224D57.8020308@chinilu.com>

On Thursday 13 March 2014 17:29:11 George Mitchell wrote:
> I currently use rsync to a separate drive to maintain a 
> backup copy, but it is not integrated into the array like n-way would 
> be, and is definitely not a perfect solution.

Could you explain how you're using rsync? I was just about to copy a 
btrfs filesystem to another disk. That filesystem has several subvolumes 
and about 100 snapshots overall. Owing to COW, this amounts to about 
1.2TB. However, I reckon that rsync doesn't know anything about COW and 
accordingly would blow up my data immensely on the destination disk.

How do I copy a btrfs filesystem preserving its complete contents? How 
do I update such a copy?

Yes, I want to keep the subvolume layout of the original and I want to 
copy all snapshots. I don't think send/receive is the answer, but it's 
likey I don't understand it well enough. I'm concerned, that a 
send/receive-based approach is not robust against mishaps.

Consider: I want to incrementally back-up a filesystem to two external 
disks. For this I'd have to for each subvolume keep a snapshot 
corresponding to its state on the backup disk. If I make any mistake in 
managing these snapshots, I can't update the external backup anymore.

Also, I don't understand whether send/receive would allow me to 
copy/update a subvolume *including* its snapshots.

Things have become a little more complicated than I had hoped for, but 
I've only been using btrfs for a couple of weeks.

Michael

-- 
Michael Schuerig
mailto:michael@schuerig.de
http://www.schuerig.de/michael/


  parent reply	other threads:[~2014-03-15 11:35 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
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 [this message]
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=1789445.UA8sCrE2Cn@fuchsia \
    --to=michael.lists@schuerig.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox