[Now the horse has left the barn, I decided to finally implement that
backup system I'd been thinking about for ages. Disk crashes can be
great motivators]
[Web-location for the living version of this document:
http://www.lartmaker.nl/rsync/]
Goal:
Producing a working network backup / cloni
This patch seems to work nicely except for the problem that if you
resync a directory that has been synced using this..
Every resource fork is resynced because OS 10.4 accepts the ._filename
and stores it properly in the resource fork but the rsync doesn't notice
this.. and decides the file is
... ._resource forks being synced over and over despite the target file
itself not moving..
Missing fact...
I am attempting a link-destination based multiple backup that creates
hard links to files that are duplicates and only moves the changed
files.. This implementation of rsync is not not
My solution is to use a separate utility called "SplitForks" on OSX,
then a unpatched rsync is used on a Mac to transfer files to a linux
box for backup.
SplitForks is a tool in OSX's Developer toolkit, which will make
those "._xyz" files on HFS+ volume.
I developed a shell script to use SplitFor
At 09:54 -0500 01-12-2005, David Powell wrote:
... ._resource forks being synced over and over despite the target
file itself not moving..
Is this Problem #4 mentioned in http://www.lartmaker.nl/rsync/ , or
something else ?
Missing fact...
I am attempting a link-destination based multiple
It is just the "performance" issue. However, this issue is unacceptable
because of the number of files I am synching.. millions.. sending all of
these resource forks is just asking for trouble... using RsyncX I only
transfer a few thousand files each session but this error just transfers
reso
