Folks,
Thinking again about the issue of
changed attributes for a file in source that is identical in content
to a file in destination that is hard linked get propagated to the
--link-dest directories
I would like to suggest a new flag, (perhaps called something like
--preserve-linked-at
Hi all,
I have a script that rsyncs files from one machine to another as part of a
periodic backup. The source file system can be changing as the backup happens
and sometimes, I get "24 - Partial transfer due to vanished source files"
errors. That error doesn't really bug me, so I mask it out in
Yeah I know, there's more I need to do to optimize. That script is
probably nearing ten years old. It's been running without a single problem
so I never bothered to revisit it, even after updating machines, I just
copy it over and keep in trucking.
On Tue, Jan 22, 2013 at 4:14 PM, Kevin Korb w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Also, if you put dates and times in the file names instead of .01,
.02, etc you don't have to do any mv's, you can easily tell when each
backup was run, and ls can tell you which the newest and oldest are.
On 01/22/13 18:12, Kevin Korb wrote:
> That i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
That is the old way that pre-dates --link-dest. Instead of cp -al
daily.02 daily.01 you can do a mkdir daily.01 then an rsync ...
- --link-dest=../daily.02 daily.01
Rsync then doesn't need any --delete and you don't bother making any
hard links that
Joe, this is specific to having a backup with rsync. The way I use links
for rsync is by not using the link (ln) command at all, but instead using
cp's build-in -l (link) option. It looks something like this:
1) delete the oldest backup (simple 'rm' command)
2) shift the rest (with 'rm') by 1, s
Thanks. Will read.
Joe
On 01/22/2013 05:31 PM, François wrote:
> Hi Joe,
>
> If you want to understand hard-links, just take a look at Wikipedia :
> http://en.wikipedia.org/wiki/Hard_link#Example
>
> I think it's pretty easy to understand.
>
> To understand how hard-links (and rsync) can help yo
Thank you! I will read it and see where to go from there.
Joe
On 01/22/2013 12:44 PM, Kevin Korb wrote:
> Here is one I wrote up for a LUG presentation that is specifically
> about doing it yourself:
> http://sanitarium.net/golug/rsync_backups_2010.html
>
> On 01/22/13 02:31, Joe wrote:
> > The
Hi Joe,
If you want to understand hard-links, just take a look at Wikipedia :
http://en.wikipedia.org/wiki/Hard_link#Example
I think it's pretty easy to understand.
To understand how hard-links (and rsync) can help you make strong incremental
backups, head over
http://blog.interlinked.org/tutor
Thanks for the reply. I know what hard and soft links are and have some
idea of how they relate to backup.
What I need is a tutorial on how all of that works with rsync. I can
see that there are a lot of considerations as to which options to use
for different situations and maybe some general st
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Here is one I wrote up for a LUG presentation that is specifically
about doing it yourself:
http://sanitarium.net/golug/rsync_backups_2010.html
On 01/22/13 02:31, Joe wrote:
> There have been a lot of posts on the list lately about issues with
> hard
11 matches
Mail list logo
