linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc MERLIN <marc@merlins.org>
To: Hugo Mills <hugo@carfax.org.uk>,
	linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Is anyone using btrfs send/receive for backups instead of rsync?
Date: Sat, 28 Dec 2013 10:07:58 -0800	[thread overview]
Message-ID: <20131228180758.GF19863@merlins.org> (raw)
In-Reply-To: <20131228173730.GA7234@carfax.org.uk>

On Sat, Dec 28, 2013 at 05:37:30PM +0000, Hugo Mills wrote:
> > Is it still being worked on, or kind of frozen/good as is?
> 
>    It's almost feature-complete: there's one version bump expected in
> the stream format, to handle files with holes in. There are probably
> still awkward bugs in there (awkward in the sense that your backups
> will fail noisily if you hit one), but for my current usage -- disk to
> disk on the same system -- it seems to work OK.
> 
>    I'm trying at the moment to hack together a working send/receive
> backup between two systems. As far as I know, the send/receive will
> work OK, but I'm having problems with firewalls and ssh tunnels right
> now. :)

Good to know, thanks.

Just curious: what happens if the destination you're syncing the
snapshot diff to, isn't quite like expected?

For instance, if I use an existing rsync destination to start syncing
btrfs snapshots to after that, and one file operation can't be applied
because let's say the destination file it's supposed to be applied to,
isn't there?

Thanks,
Marc
-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
                                      .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/                         | PGP 1024R/763BE901

  parent reply	other threads:[~2013-12-28 18:08 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-28 17:19 Is anyone using btrfs send/receive for backups instead of rsync? Marc MERLIN
2013-12-28 17:37 ` Hugo Mills
2013-12-28 18:01   ` Emil Karlson
2013-12-28 19:34     ` Richard Michael
2013-12-28 19:52       ` Emil Karlson
2013-12-28 20:34         ` Richard Michael
2013-12-28 23:11           ` Chris Murphy
2013-12-28 23:55             ` Emil Karlson
2013-12-29  0:08               ` Chris Murphy
2013-12-29 12:39             ` Duncan
2013-12-30  0:38               ` systemd-journal, nodatacow, was: " Chris Murphy
2013-12-30  8:07                 ` Duncan
2013-12-30 16:00                 ` Chris Mason
2013-12-28 18:07   ` Marc MERLIN [this message]
2013-12-28 18:20     ` Marc MERLIN
2013-12-30 16:05       ` Chris Mason
2013-12-30 16:17         ` Marc MERLIN
2013-12-30 16:26           ` Chris Mason
2013-12-30 17:10             ` Marc MERLIN
2013-12-30 17:48               ` Chris Murphy
2013-12-30 17:57                 ` Marc MERLIN
2013-12-30 18:39                   ` Chris Murphy
2014-01-03 20:15                   ` Marc MERLIN
2014-01-03 20:35                     ` Chris Mason
2014-01-07 10:49     ` Is anyone using btrfs send/receive howto? Marc MERLIN
2014-01-07 10:53       ` Hugo Mills
2014-01-08  8:02         ` Marc MERLIN
2014-03-21 17:29           ` Send/Receive howto and script for others to use (was Re: Is anyone using btrfs send/receive) Marc MERLIN
2014-03-22 19:44             ` Brendan Hide
2014-03-22 19:53               ` Brendan Hide
2014-03-22 20:00               ` Marc MERLIN
2014-03-22 21:02                 ` Brendan Hide
2014-03-22 21:11                   ` Marc MERLIN
2014-03-23  7:12                     ` Brendan Hide

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=20131228180758.GF19863@merlins.org \
    --to=marc@merlins.org \
    --cc=hugo@carfax.org.uk \
    --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;
as well as URLs for NNTP newsgroup(s).