From: Christoph Biedl <linux-kernel.bfrz@manchmal.in-ulm.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: backup best practise?
Date: Fri, 2 Jan 2026 11:39:17 +0100 [thread overview]
Message-ID: <1767349993@msgid.manchmal.in-ulm.de> (raw)
In-Reply-To: <20260101234624.GA1955478@tik.uni-stuttgart.de>
Heya,
Ulli Horlacher wrote...
> What is the best practise for backup of a local btrfs file system?
send/receive was already mentioned, and despite a higher cost of setting
things up I'd never want to miss the efficiency of incremental syncs.
And of course it allows remote replication as well.
> In my case, I have 2 disks: disk one contains a /home btrfs filesystem,
> disk two contins a /backup btrfs filesystem.
> So far I use:
> rsync -a --delete /home /backup
>
> The drawback of this methode is: In /home there are also *big* VMs which
> will be copied every time even if they have changed only a few bytes,
> because rsync works file based.
A bit offtopic here, check --inplace, rsync's support for this has
improved a lot over the past years. Still, check the manpage for various
caveats.
Christoph
prev parent reply other threads:[~2026-01-02 10:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-01 23:46 backup best practise? Ulli Horlacher
2026-01-02 2:37 ` Nicholas D Steeves
2026-01-02 7:34 ` Andrei Borzenkov
2026-01-02 10:39 ` Christoph Biedl [this message]
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=1767349993@msgid.manchmal.in-ulm.de \
--to=linux-kernel.bfrz@manchmal.in-ulm.de \
--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