From: Bill Davidsen <davidsen@tmr.com>
To: Wolfgang Denk <wd@denx.de>
Cc: "Dean S. Messing" <deanm@sharplabs.com>, linux-raid@vger.kernel.org
Subject: Re: Backups w/ rsync
Date: Fri, 28 Sep 2007 12:50:43 -0400 [thread overview]
Message-ID: <46FD30E3.7090809@tmr.com> (raw)
In-Reply-To: <20070928145718.7320C24769@gemini.denx.de>
Wolfgang Denk wrote:
> Dear Bill,
>
> in message <46FD1442.70707@tmr.com> you wrote:
>
>> Be aware that rsync is useful for making a *copy* of your files, which
>> isn't always the best backup. If the goal is to preserve data and be
>> able to recover in time of disaster, it's probably not optimal, while if
>> you need frequent access to old or deleted files it's fine.
>>
>
> If you want to do real backups you should use real tools, like bacula
> etc.
>
>
>> Now you can do an incremental (since last full or incremental) or
>> partial (since last full):
>>
>> touch bkup_incr_new
>> timestamp=$(date +%Y%m%d-%T)
>> find /home -cnewer bkup_incr | cpio -o -Hcrc |
>> gzip -3 >/mnt/USBbkup/incr-$timestamp &&
>> mv -f bkup_incr_new bkup_incr
>>
>> timestamp=$(date +%Y%m%d-%T)
>> find /home -cnewer bkup_full | cpio -o -Hcrc |
>> gzip -3 >/mnt/USBbkup/part-$timestamp
>>
>
> Now have Johnny Loser downloading some stuff, say:
>
> $ wget -N ftp://ftp.kernel.org/pub/linux/kernel/v2.6/linux-2.6.12.tar.gz
>
> Are you aware that this file will never be backed up by your script?
>
> Also, what about permission / owner changes etc.?
>
Do note the use of -cnewer, which is *not* the same as the modified
time, and which exactly addresses your points. Ownership changes, etc,
will causes a backup of the contents as well, but they will be preserved.
> A backup tool should never work based on timestamps alone.
>
Feel free to use a tool which does a checksum of every file if you feel
it's needed on your system. I'm not trying to defend against people
playing with ctime or system time of day, just protect normal day-to-day
data.
> Best regards,
>
> Wolfgang Denk
>
>
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
next prev parent reply other threads:[~2007-09-28 16:50 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-18 23:09 Help: very slow software RAID 5 Dean S. Messing
2007-09-19 0:05 ` Justin Piszcz
2007-09-19 1:49 ` Dean S. Messing
2007-09-19 8:38 ` Justin Piszcz
2007-09-19 17:49 ` Dean S. Messing
2007-09-19 18:25 ` Justin Piszcz
2007-09-19 23:31 ` Dean S. Messing
2007-09-20 8:25 ` Justin Piszcz
2007-09-20 18:16 ` Michal Soltys
2007-09-20 19:06 ` Dean S. Messing
2007-09-20 15:33 ` Bill Davidsen
2007-09-20 18:47 ` Dean S. Messing
2007-09-20 21:08 ` Michael Tokarev
2007-09-21 0:58 ` Dean S. Messing
2007-09-21 13:00 ` Bill Davidsen
2007-09-21 20:01 ` Dean S. Messing
2007-09-21 20:21 ` Dean S. Messing
2007-09-25 9:31 ` Goswin von Brederlow
2007-09-25 18:16 ` Dean S. Messing
2007-09-25 21:46 ` Goswin von Brederlow
2007-09-25 23:50 ` Dean S. Messing
2007-09-26 1:45 ` Goswin von Brederlow
2007-09-27 6:23 ` Dean S. Messing
2007-09-27 9:51 ` Michal Soltys
2007-09-27 22:10 ` Backups w/ rsync (was: Help: very slow software RAID 5.) Dean S. Messing
2007-09-28 7:57 ` Backups w/ rsync Michael Tokarev
2007-09-28 10:23 ` Goswin von Brederlow
2007-09-28 11:18 ` Michal Soltys
2007-09-28 12:47 ` Goswin von Brederlow
2007-09-28 14:17 ` Michal Soltys
2007-09-29 0:11 ` Dean S. Messing
2007-09-29 8:43 ` Michael Tokarev
2007-09-28 14:48 ` Bill Davidsen
2007-09-28 14:57 ` Wolfgang Denk
2007-09-28 16:50 ` Bill Davidsen [this message]
2007-10-01 4:45 ` Michal Soltys
2007-09-28 15:11 ` Jon Nelson
2007-09-28 16:25 ` Bill Davidsen
2007-09-28 16:52 ` Jon Nelson
2007-09-27 22:40 ` Help: very slow software RAID 5 Bill Davidsen
2007-09-28 23:38 ` Dean S. Messing
2007-09-29 14:52 ` Bill Davidsen
2007-09-27 22:17 ` Bill Davidsen
2007-09-28 23:21 ` Dean S. Messing
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=46FD30E3.7090809@tmr.com \
--to=davidsen@tmr.com \
--cc=deanm@sharplabs.com \
--cc=linux-raid@vger.kernel.org \
--cc=wd@denx.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 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).