linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sam Bull <sam.hacking@sent.com>
To: Russell Coker <russell@coker.com.au>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Questions on incremental backups
Date: Fri, 18 Jul 2014 13:56:58 +0100	[thread overview]
Message-ID: <1405688218.3085.16.camel@s-Air> (raw)
In-Reply-To: <e1b3b459-ea44-4272-9320-4cb5218b3966@email.android.com>

[-- Attachment #1: Type: text/plain, Size: 1614 bytes --]

Thanks for the replies, I think that's most of the questions answered.
I'll not bother backing up any VMs, as they won't contain anything worth
backing up. Can anybody answer the last couple of remaining questions?

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?

> 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?

If I want to create a backup view, I could start with just a file view
of the most recent snapshot, but is there a way I can quickly get a list
of additional files in the other snapshots that are not present in the
most recent one (files that have been deleted)?



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)?

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2014-07-18 12:57 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 [this message]
2014-07-18 13:40     ` Russell Coker
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=1405688218.3085.16.camel@s-Air \
    --to=sam.hacking@sent.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=russell@coker.com.au \
    /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).