From: Michael Tokarev <mjt@tls.msk.ru>
To: "Dean S. Messing" <deanm@sharplabs.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Backups w/ rsync
Date: Sat, 29 Sep 2007 12:43:58 +0400 [thread overview]
Message-ID: <46FE104E.3080608@msgid.tls.msk.ru> (raw)
In-Reply-To: <20070929001118.D0F24102F5B@medulla.enet.sharplabs.com>
Dean S. Messing wrote:
> Michael Tokarev writes:
[]
> : the procedure is something like this:
> :
> : cd /backups
> : rm -rf tmp/
> : cp -al $yesterday tmp/
> : rsync -r --delete -t ... /filesystem tmp
> : mv tmp $today
> :
> : That is, link the previous backup to temp (which takes no space
> : except directories), rsync current files to there (rsync will
> : break links for changed files), and rename temp to $today.
>
> Very nice. The breaking of the hardlink is the key. I wondered about
> this when Michal using rsync yesterday. I just tested the idea. It
> does indeed work.
Well, others in this thread already presented other, simpler ways,
namely using --link-dest rsync option. I was just too lazy to read
the man page, but I already knew other tools can do the work ;)
> One question: why do you not use "-a" instead of "-r -t"? It would
> seem that one would want to preserve permissions, and group and user
> ownerships. Also, is there a reason to _not_ preserve sym-links
> in the backup. Your script appears to copy the referent.
Note the above -- "SOMETHING like this". I was typing from memory,
it's not an actual script, just to show an idea. Sure real script
does more than that, including error checking too.
/mjt
next prev parent reply other threads:[~2007-09-29 8:43 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 [this message]
2007-09-28 14:48 ` Bill Davidsen
2007-09-28 14:57 ` Wolfgang Denk
2007-09-28 16:50 ` Bill Davidsen
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=46FE104E.3080608@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=deanm@sharplabs.com \
--cc=linux-raid@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).