All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc MERLIN <marc@merlins.org>
To: Axel Burri <axel@tty0.ch>
Cc: Martin Steigerwald <martin@lichtvoll.de>, linux-btrfs@vger.kernel.org
Subject: Re: Anyone tried out btrbk yet?
Date: Sat, 11 Jul 2015 20:55:23 -0700	[thread overview]
Message-ID: <20150712035523.GI5274@merlins.org> (raw)
In-Reply-To: <559FA280.8090309@tty0.ch>

On Fri, Jul 10, 2015 at 12:46:24PM +0200, Axel Burri wrote:
> On 2015-07-09 14:26, Martin Steigerwald wrote:
> 
> > Well I may try it for one of my BTRFS volumes in addition to the rsync 
> > backup for now. I would like to give all options on command line, but well, 
> > maybe it can completely replace my current script if I put everything in its 
> > configuration.
> 
> One reason why btrbk exists is that I wanted to have all my backups
> configured in a config file. I use btrbk to backup several hosts to
> several backup locations (around 20 subvolumes), which made setting
> everything up with command-line options very cumbersome.
> 
> For simpler setups you might be better off with command-line based tools
> (e.g. Marcs "btrfs-subvolume-backup", which I like for it's smallness).

I just had another look at btrbk, and it's obviously a lot more
featureful. It's almost 10 times bigger in lines of code than
btrfs-subvolume-backup :)

Anyway, to others, if you're happy using a tool that just does that you
need without having to dig into it and without you caring how btrfs
send/receive, works, btrbk looks like the better choice.

If you'd like something short-ish to look at and see how it works and/or
want something simple in shell you can modify quickly, btrfs-subvolume-backup
might be better for you.

Hope that helps others.

Marc
-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
                                      .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/                         | PGP 1024R/763BE901

  reply	other threads:[~2015-07-12  3:55 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-09 12:26 Anyone tried out btrbk yet? Martin Steigerwald
2015-07-09 17:12 ` Henri Valta
2015-07-09 17:17 ` Marc MERLIN
2015-07-10  1:35   ` Donald Pearson
2015-07-10  1:38     ` Donald Pearson
2015-07-10  4:02       ` Paul Harvey
2015-07-10 10:46 ` Axel Burri
2015-07-12  3:55   ` Marc MERLIN [this message]
2015-07-13  0:42     ` Marc MERLIN
2015-07-15  0:03       ` Paul Harvey
2015-07-15  3:14         ` Marc MERLIN
2015-07-15  8:00           ` Sander
2015-07-15 14:42             ` Donald Pearson
2015-07-15 18:02               ` Donald Pearson
2015-07-15 21:49                 ` Marc MERLIN
2015-07-20  5:15                   ` Donald Pearson
2015-07-20  8:28                     ` Duncan
2015-07-20 13:33                       ` Donald Pearson
2015-07-21  9:29                         ` Duncan
2015-07-22  1:29                           ` Donald Pearson
2015-07-25 13:27                             ` Donald Pearson
2015-07-26  5:39                               ` Duncan
2015-07-15 21:48               ` Marc MERLIN

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=20150712035523.GI5274@merlins.org \
    --to=marc@merlins.org \
    --cc=axel@tty0.ch \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=martin@lichtvoll.de \
    /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.