From: Marc MERLIN <marc@merlins.org>
To: Cao jin <caoj.fnst@cn.fujitsu.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Question about "btrfs send/receive"
Date: Tue, 23 Jun 2015 20:24:23 -0700 [thread overview]
Message-ID: <20150624032423.GH20517@merlins.org> (raw)
In-Reply-To: <5589078B.2090806@cn.fujitsu.com>
On Tue, Jun 23, 2015 at 03:15:23PM +0800, Cao jin wrote:
> Hi all,
> I am considering implement the btrfs send/receive command in
> libguestfs(http://libguestfs.org/), and found that incremental send
> seems pretty complicated. So my questions is:
> 1. What is the most usually usage of btrfs send/receive?
> 2. Does it make sense to implement the simplest form?
> $ btrfs send -f sent_file subvol
Sure, have a look at this:
http://marc.merlins.org/perso/btrfs/2014-03.html#Btrfs-Tips_-Doing-Fast-Incremental-Backups-With-Btrfs-Send-and-Receive
Cheers,
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/
next prev parent reply other threads:[~2015-06-24 3:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-23 7:15 Question about "btrfs send/receive" Cao jin
2015-06-24 3:24 ` Marc MERLIN [this message]
2015-06-24 3:40 ` Cao jin
2015-06-24 4:21 ` Marc MERLIN
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=20150624032423.GH20517@merlins.org \
--to=marc@merlins.org \
--cc=caoj.fnst@cn.fujitsu.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