From: Marc MERLIN <marc@merlins.org>
To: Brendan Hide <brendan@swiftspirit.co.za>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Copying related snapshots to another server with btrfs send/receive?
Date: Sun, 4 May 2014 00:28:29 -0700 [thread overview]
Message-ID: <20140504072829.GK9061@merlins.org> (raw)
In-Reply-To: <5365E932.20602@swiftspirit.co.za>
On Sun, May 04, 2014 at 09:16:02AM +0200, Brendan Hide wrote:
> Sending one-at-a-time, the shared-data relationship will be kept by
> using the -p (parent) parameter. Send will only send the differences
> and receive will create a new snapshot, adjusting for those
> differences, even when the receive is run on a remote server.
>
> $ btrfs send backup | btrfs receive $path/
> $ btrfs send -p backup backup.sav1 | btrfs receive $path/
> $ btrfs send -p backup.sav1 backup.sav2 | btrfs receive $path/
> $ btrfs send -p backup.sav2 backup.sav3 | btrfs receive $path/
> $ btrfs send -p backup.sav3 backup.sav4 | btrfs receive $path/
So this is exactly the same than what I do incremental backups with
brrfs send, but -p only works if the snapshot is read only, does it not?
I do use that for my incremental syncs and don't mind read only
snapshots there, but if I have read/write snapshots that are there for
other reasons than btrfs send incrementals, can I still send them that
way with -p?
(I thought that wouldn't work)
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
next prev parent reply other threads:[~2014-05-04 7:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-04 3:12 Copying related snapshots to another server with btrfs send/receive? Marc MERLIN
2014-05-04 7:16 ` Brendan Hide
2014-05-04 7:28 ` Marc MERLIN [this message]
2014-05-04 7:54 ` Brendan Hide
2014-05-05 1:04 ` Marc MERLIN
2014-05-05 3:24 ` Duncan
2014-05-07 7:51 ` 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=20140504072829.GK9061@merlins.org \
--to=marc@merlins.org \
--cc=brendan@swiftspirit.co.za \
--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.