From: Marc MERLIN <marc@merlins.org>
To: linux-btrfs@vger.kernel.org
Subject: Copying related snapshots to another server with btrfs send/receive?
Date: Sat, 3 May 2014 20:12:31 -0700 [thread overview]
Message-ID: <20140504031231.GG9061@merlins.org> (raw)
Another question I just came up with.
If I have historical snapshots like so:
backup
backup.sav1
backup.sav2
backup.sav3
If I want to copy them up to another server, can btrfs send/receive
let me copy all of the to another btrfs pool while keeping the
duplicated block relationship between all of them?
Note that the backup.sav dirs will never change, so I won't need
incremental backups on those, just a one time send.
I believe this is supposed to work, correct?
The only part I'm not clear about is am I supposed to copy them all at
once in the same send command, or one by one?
If they had to be copied together and if I create a new snapshot of
backup: backup.sav4
If I use btrfs send to that same destination, is btrfs send/receive indeed
able to keep the shared block relationship?
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 reply other threads:[~2014-05-04 5:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-04 3:12 Marc MERLIN [this message]
2014-05-04 7:16 ` Copying related snapshots to another server with btrfs send/receive? Brendan Hide
2014-05-04 7:28 ` Marc MERLIN
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=20140504031231.GG9061@merlins.org \
--to=marc@merlins.org \
--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).