Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'A summary hint of rsync-related information' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
A summary hint of rsync-related information
Authored by: olve on Jul 21, '03 01:04:52PM

I agree that psync does a "cleaner" job with OSX and in my experience it is the only option if you're going to a non-HFS volume, but rsync wins out in terms of options.

FYI, I run regular "local" mirror backups of several volumes mounted from remote machines. I use rsync_hfs for afp:// volumes and psync for smb:// volumes. Of course, these volumes must always be mounted for this to work. I would of course prefer an rsync_hfs server where the individual clients contact and add to the backup, but as an alternative, the "-e ssh" option in rsync will work, but you have to allow remote root access for get full backups. With psync, the volumes must be mounted.

I have also noticed the malloc errors in rsync when you have a file for which there is no read permission. Is this perhaps the issue more than max file count? On the Linux side, I regularly rsync 80 GB volumes with lots of file without any problems.

As a side note, it is ironic that Retrospect makes preference files in user directories that are only admin accessible and this foils rsync_hfs backups! (I think this is only in the directory of a user that set up the Retrospect job and may only apply if one also sets Retrospect to required admin authentication for change, but am not sure yet).

Olve



[ Reply to This | # ]