From: Sam Bull <sam.hacking@sent.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Questions on incremental backups
Date: Sun, 20 Jul 2014 17:56:45 +0100 [thread overview]
Message-ID: <1405875405.2789.4.camel@s-Air> (raw)
In-Reply-To: <CAB=7dhkcbfGrwSwq=7f_ML-DjPZY56VX08_Xz15MSG_4ygDk7A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 171 bytes --]
Thanks everyone for the responses. I'll start setting up my backup
strategy in 2 or 3 weeks. I'll give the diff and unionFS tips a go, and
report back on any progress.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2014-07-20 16:56 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
2014-07-18 14:27 ` Mike Hartman
2014-07-20 16:56 ` Sam Bull [this message]
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=1405875405.2789.4.camel@s-Air \
--to=sam.hacking@sent.com \
--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 NNTP newsgroup(s).