From: HAN Yuwei <hrx@bupt.moe>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Fwd: snapshots of subvolumes recursivly?
Date: Mon, 13 May 2024 16:27:22 +0800 [thread overview]
Message-ID: <4177B1D395584346+0c96848e-da45-489b-b349-6fbc5befcefe@bupt.moe> (raw)
In-Reply-To: <20240513075016.GC94789@tik.uni-stuttgart.de>
[-- Attachment #1.1.1: Type: text/plain, Size: 846 bytes --]
Forward this message to mailing-list
-------- 转发的消息 --------
主题: Re: snapshots of subvolumes recursivly?
日期: Mon, 13 May 2024 09:50:16 +0200
From: Ulli Horlacher <framstag@rus.uni-stuttgart.de>
收件人: HAN Yuwei <hrx@bupt.moe>
I am not able any more to reply to the mailing list:
<linux-btrfs@vger.kernel.org>: host smtp.subspace.kernel.org[44.238.234.78]
said: 550 5.7.1 Your message looked spammy to us. Please check
https://subspace.kernel.org/etiquette.html and resend. (in reply to end of
DATA command)
--
Ullrich Horlacher Server und Virtualisierung
Rechenzentrum TIK
Universitaet Stuttgart E-Mail: horlacher@tik.uni-stuttgart.de
Allmandring 30a Tel: ++49-711-68565868
70569 Stuttgart (Germany) WWW: https://www.tik.uni-stuttgart.de/
[-- Attachment #1.1.2: ForwardedMessage.eml --]
[-- Type: message/rfc822, Size: 2475 bytes --]
From: Ulli Horlacher <framstag@rus.uni-stuttgart.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: snapshots of subvolumes recursivly?
Date: Mon, 13 May 2024 09:37:29 +0200
Message-ID: <20240513073729.GA94789@tik.uni-stuttgart.de>
On Mon 2024-05-13 (12:19), HAN Yuwei wrote:
> 圚 2024/5/13 4:39, Ulli Horlacher 写é":
>
> > I have asked a similar question 2019-07-05, but maybe meanwhile there is a
> > solution...
> >
> > I want to backup btrfs filesystems with IBM Spectrum Protect and restic,
> > both are file based.
> >
> > Copying files which are in write-open state will lead to file corruption.
> > Therefore my idea is: create a snapshot and run the backup on the snapshot.
>
> You could use "btrfs send" to send whole snapshot instead of file.
I MUST use IBM Spectrum Protect or restic, because the backup
storage is a (multi-million dollar) tape library.
> > I could write a script which creates snapshots of the subvolumes
> > (recursivly), but maybe there is already such a program?
> > Or another solution for this problem?
>
> From what I understand, subvolume created a way to split your "snapshot
> zone" for better data management(e.g. you can snapshot / without
> including /home or /var). This is intented.
>
> So if you want to backup sv1 sv2, why you created subvolume in the first
> place?
This is only a simple example to explain the problem.
I have hundreds of hosts which use btrfs subvolumes intensivly.
For example SLES splits the / filesystem in a dozen subvolumes.
I cannot change this setup.
And users may create (sub-)subvolumes, too. I cannot stop them in doing so.
But I must organize the backup. It's up to me :-}
--
Ullrich Horlacher Server und Virtualisierung
Rechenzentrum TIK
Universitaet Stuttgart E-Mail: horlacher@tik.uni-stuttgart.de
Allmandring 30a Tel: ++49-711-68565868
70569 Stuttgart (Germany) WWW: https://www.tik.uni-stuttgart.de/
REF:<6B5555BE532EFFBF+03c904d1-3111-40d6-9266-8c02c35b6cd4@bupt.moe>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
parent reply other threads:[~2024-05-13 8:27 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20240513075016.GC94789@tik.uni-stuttgart.de>]
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=4177B1D395584346+0c96848e-da45-489b-b349-6fbc5befcefe@bupt.moe \
--to=hrx@bupt.moe \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).