From: Martin <m_btrfs@ml1.co.uk>
To: linux-btrfs@vger.kernel.org
Subject: btrfs-send-receive vs rsync for (incremental/full) backups
Date: Fri, 13 Dec 2013 19:44:16 +0000 [thread overview]
Message-ID: <l8fo25$a4h$1@ger.gmane.org> (raw)
OK... So for backing up across a local network to a second physical host...
Is btrfs-send-receive stable enough now to be used?
How does send-receive compare to using rsync for backups?
Any comments please from those using such things?
Thanks,
Martin
next reply other threads:[~2013-12-13 19:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-13 19:44 Martin [this message]
2013-12-13 20:35 ` btrfs-send-receive vs rsync for (incremental/full) backups Hugo Mills
2013-12-13 21:30 ` Chris Murphy
2013-12-13 22:55 ` Hugo Mills
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='l8fo25$a4h$1@ger.gmane.org' \
--to=m_btrfs@ml1.co.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 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.