From: "Senén Vidal Blanco" <senenvidal@sgisoft.com>
To: linux-btrfs@vger.kernel.org
Subject: Storage and snapshots as historical yearly
Date: Mon, 11 Sep 2017 20:17:01 +0200 [thread overview]
Message-ID: <9208764.SjP1vfhOIA@pcsenen> (raw)
[-- Attachment #1: Type: text/plain, Size: 1293 bytes --]
I am trying to implement a system that stores the data in a unit (A) with
BTRFS format that is untouchable and that future files and folders created or
modified are stored in another physical unit (B) with BTRFS format.
Each year the new files will be moved to store A and start over.
The idea is that a duplicate of disk A can be made to keep it in a safe place
and that the files stored there can not be modified until the mixture of (A) and
(B) is made.
I have looked for information on this but I do not see it very clear. Both
"SEND" and "RECEIVE" do the opposite case to what interests me.
I have also seen that you could try to get a RAID 0 but I am afraid that the
data in A will not remain intact if the system performs a "BALANCE" at some
point and mixes data between (A) and (B).
It is assumed that both the (A) and (B) data will be displayed in the same
structure transparently, for example in "/ home".
-------------------------------
| HOME |
| ------------ ------------ |
| | | | | |
| | | | | |
| | DISK (A) | | DISK (B) | |
| | BTRFS | | BTRFS | |
| | | | | |
| ------------ ------------ |
-------------------------------
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next reply other threads:[~2017-09-11 18:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 18:17 Senén Vidal Blanco [this message]
2017-09-11 18:49 ` Storage and snapshots as historical yearly Austin S. Hemmelgarn
2017-09-11 21:36 ` Pete
2017-09-12 12:16 ` Austin S. Hemmelgarn
2017-09-13 11:51 ` Pete
2017-09-13 12:26 ` Austin S. Hemmelgarn
2017-09-19 19:09 ` Senén Vidal Blanco
2017-09-12 3:34 ` Andrei Borzenkov
2017-09-19 11:49 ` Senén Vidal Blanco
2017-09-19 18:33 ` Andrei Borzenkov
2017-09-19 19:19 ` Austin S. Hemmelgarn
2017-09-21 10:07 ` Senén Vidal Blanco
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=9208764.SjP1vfhOIA@pcsenen \
--to=senenvidal@sgisoft.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 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.