From: GEO <1g2e3o4@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Incremental backup over writable snapshot
Date: Thu, 27 Feb 2014 14:10:25 +0100 [thread overview]
Message-ID: <1682169.l7oZKuLmJy@linuxpc> (raw)
In-Reply-To: <17860756.QfG9CfNMqv@linuxpc>
Does anyone have a technical info regarding the reliability of the incremental
backup process using the said method?
(Apart from all the recommendations not to do it that way)
So the question I am interested in: Should it work or not?
I did some testing myself and it seemed to work, however I cannot find out if
it backs up unnecessary blocks and thus making the incremental step space
inefficient.
That information would help me very much!
Thank you very much!
On Wednesday 19 February 2014 14:45:57 GEO wrote:
> Hi,
>
> As suggested in another thread, I would like to know the reliability of the
> following backup scheme:
>
> Suppose I have a subvolume of my homedirectory called @home.
>
> Now I am interested in making incremental backups of data in home I am
> interested in, but not everything, so I create a normal snapshot of @home
> called @home-w and delete the files/folders I am not interested in backing
> up. After that I create a readonly snapshot of @home-w called @home-r, that
> I sent to my target volume with btrfs send.
>
> After that is done, I do regular backups, by always going over the writeable
> snapshot where I remove always the same directories I am not interested and
> send the difference to the target volume with btrfs send -p @home-r
> @home-r-1| btrfs receive /path/of/target/volume.
>
> I do not like the idea of making subvolumes of all directories I am not
> interested in backing up.
>
> So what I would like to know now is the following: Could there be drawbacks
> of doing this resp. could I further optimize my backup strategy, as I
> experienced it takes a while for deleting large files in the writeable
> snapshot (What does it write there?)
>
> Could my method somehow lead to inefficiency in terms of the disk space used
> at the target volume (I mean, could the deleting cause a change, so that
> more is actually transferred as change, than in reality is?)?
>
> One last question would be: Is there a quick way I could verify the local
> read only snapshot used last time is the same as the one synced to the
> target volume last time?
>
>
> Thank you for your support and the great work!
next prev parent reply other threads:[~2014-02-27 13:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-19 13:45 Incremental backup over writable snapshot GEO
2014-02-19 17:00 ` Chris Murphy
2014-02-19 18:57 ` GEO
2014-02-20 13:20 ` GEO
2014-02-20 23:04 ` Kai Krakow
[not found] ` <2285169.jbztTl7OC0@linuxpc>
2014-02-19 17:26 ` Chris Murphy
[not found] ` <16991840.tqyQc6bZHr@linuxpc>
2014-02-19 17:51 ` Chris Murphy
2014-02-19 20:20 ` Kai Krakow
2014-02-20 3:31 ` Kai Krakow
2014-02-20 11:03 ` Duncan
2014-02-20 21:16 ` Kai Krakow
2014-02-21 14:44 ` GEO
2014-02-21 18:56 ` Kai Krakow
2014-02-27 13:10 ` GEO [this message]
2014-02-28 6:54 ` Duncan
2014-02-27 14:36 ` GEO
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=1682169.l7oZKuLmJy@linuxpc \
--to=1g2e3o4@gmail.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).