From: Russell Coker <russell@coker.com.au>
To: Sam Bull <sam.hacking@sent.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Questions on incremental backups
Date: Fri, 18 Jul 2014 23:40:07 +1000 [thread overview]
Message-ID: <1483007.OXNgJN24dh@xev> (raw)
In-Reply-To: <1405688218.3085.16.camel@s-Air>
On Fri, 18 Jul 2014 13:56:58 Sam Bull wrote:
> On ven, 2014-07-18 at 14:35 +1000, Russell Coker wrote:
> > Ignoring directories in send/recv is done by subvol. Even if you use
> > rsync it's a good idea to have different subvols for directory trees
> > with different backup requirements.
>
> So, an inner subvol won't be backed up? If I wanted a full backup, I
> would presumably get snapshots of each subvol separately, right?
If you use btrfs send/recv then it won't get the inner subvol. If you use
rsync then by default it goes through the entire directory tree unless you use
the -x option.
> > Displaying backups is an issue of backup software. It is above the
> > level that BTRFS development touches. While people here can probably
> > offer generic advice on backup software it's not the topic of the
> > list.
>
> As said, I don't mind developing the software. But, is the required
> information easily available? Is there a way to get a diff, something
> like a list of changed/added/removed files between snapshots?
Your usual diff utility will do it. I guess you could parse the output of
btrfs send.
> And, finally, nobody has mentioned on the possibility of merging
> multiple snapshots into a single snapshot. Would this be possible, to
> create a snapshot that contains the most recent version of each file
> present across all of the snapshots (including files which may be
> present in only one of the snapshots)?
There is no btrfs functionality for that. But I'm sure you could do something
with standard Unix utilities and copying files around.
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/
next prev parent reply other threads:[~2014-07-18 13:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-17 20:12 Questions on incremental backups Sam Bull
2014-07-18 4:35 ` Russell Coker
2014-07-18 7:36 ` Bob Williams
2014-07-18 10:45 ` Duncan
2014-07-18 10:55 ` Roman Mamedov
[not found] ` <TmvW1o01t4NXQGV01mvYsU>
2014-07-18 12:34 ` Duncan
2014-07-18 13:05 ` Roman Mamedov
2014-07-18 14:28 ` Imran Geriskovan
2014-07-18 12:56 ` Sam Bull
2014-07-18 13:40 ` Russell Coker [this message]
2014-07-18 14:27 ` Mike Hartman
2014-07-20 16:56 ` Sam Bull
2014-07-18 17:31 ` Daniel Mizyrycki
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=1483007.OXNgJN24dh@xev \
--to=russell@coker.com.au \
--cc=linux-btrfs@vger.kernel.org \
--cc=sam.hacking@sent.com \
/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).