linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Anton Mitterer <calestyo@scientia.org>
To: linux-btrfs@vger.kernel.org
Subject: back&forth send/receiving?
Date: Fri, 03 Feb 2023 17:42:02 +0100	[thread overview]
Message-ID: <10fd619ccbe568df4344b6b1d93f061bc493d396.camel@scientia.org> (raw)

Hey.

I've had asked[0] this a while ago already and back then the conclusion
seems to have been that it wasn't (yet) possible but could in principle
be done.

The idea was that one main usage of btrfs' send/receive is probably
making incremental backups.

So one might have a setup, where a master is send/received to multiple
copies of that like in:

master-+-> copy1
       |-> copy2
       \-> copy3

with those all being different storage mediums.

At some point, master's HDD may e.g. break or at least reach an age
where one wants to replace it with a new one.
So either one would make e.g. copy1 the new master, or buy new HDD for
that, while keeping all the other copyN.

Problem is now, how to best continue with the above schema?

Either one just uses dd and copy over the old master to the new one
(keeping the very same btrfs).
This of course doesn't work if the old master really broke. And even if
it didn't it may be impractical (consider e.g. a 20 TB HDD which is
only half filled - why copying 10TB of empty space).


What one would IMO want is, that send/receive also works like that:
a) copy1/new-master-+-> copy2
                    |-> copy3
                    \-> copy4 (new)

b) once:
   copy1 ---> new-master

   following that: 
   new-master-+-> copy1
              |-> copy2
              \-> copy3


Did anything change with respect to v2 send/receive? Or would it be
possible to get such feature sooner or later? :-)


Thanks,
Chris.



[0] https://lore.kernel.org/linux-btrfs/157ed91bb66820d1fef89eb05d00e65c25607938.camel@scientia.net/

             reply	other threads:[~2023-02-03 16:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-03 16:42 Christoph Anton Mitterer [this message]
2023-02-04  6:10 ` back&forth send/receiving? Andrei Borzenkov
2023-02-06  3:07   ` Christoph Anton Mitterer
2023-02-06  4:16     ` Andrei Borzenkov
2023-02-06  4:31       ` Christoph Anton Mitterer
2023-02-06  6:46         ` Andrei Borzenkov
2023-02-17 17:12           ` Christoph Anton Mitterer
2023-02-17 17:25             ` Andrei Borzenkov
2023-02-18  0:29               ` Christoph Anton Mitterer
2023-02-18  6:57                 ` Andrei Borzenkov

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=10fd619ccbe568df4344b6b1d93f061bc493d396.camel@scientia.org \
    --to=calestyo@scientia.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).