From: GEO <1g2e3o4@gmail.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Incremental backup over writable snapshot
Date: Thu, 20 Feb 2014 14:20:16 +0100 [thread overview]
Message-ID: <2091546.7UkK3HMHjX@linuxpc> (raw)
In-Reply-To: <EEA604EA-983B-4F5F-88B5-4FD229FEC61F@colorremedies.com>
@Kai Krakow: I accept your opinion and thank you for your answer.
However I have special reasons doing so. I could name you a few use cases.
For example I do not need to backup search indexes as they mess up over time,
so I simple recreate the cache in case of a new install.
I know most of the settings I set and I know exactly what missing directories
break what in case of deletion, because I have tried so various times.
This is not supposed to be a system backup, or a "home" backup, but a backup
of my data (documents, videos etc.).
I know hidden directories contain mails etc. but I know exactly where my mails
are (most of them imap anyway) and I would include them in the backup.
So I am looking for a different use case.
Anyway, I know most of you won't like my idea, but my question was, if I do
everything right (and do not delete the wrong stuff out of stupidity), if the
result would be as reliable as doing your approach, so please consider that as
a technical question, even if you strongly dislike the idea.
So my initial question would remain: does the deleting of some stuff change the
whole snapshot in a way, that the increment step would be screwed, which means
I would back up blocks, that are not new.
I do not have the expertise to check out the code and answer my question
myself, so I would like to hear the opinion of the devs whether my way should
work in theory or not, regardless of the fact that the use case has not been
tested and is not recommended.
Thank you very much for your opinions.
next prev parent reply other threads:[~2014-02-20 13:20 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
[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-19 18:57 ` GEO
2014-02-20 13:20 ` GEO [this message]
2014-02-20 23:04 ` Kai Krakow
2014-02-27 13:10 ` GEO
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=2091546.7UkK3HMHjX@linuxpc \
--to=1g2e3o4@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.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).