![]() ![]() It basically encodes the extra stuff into the extended attributes on the remote system. For this, rsync has the –fake-super option. The basic problem is that there are still a bunch of OSX specific metadata bits that rsync on the Mac can read, but the linux end does not know how to store them. Now, it works a bit better, but a lot of stuff still fails. Mount -t ext3 -o user_xattr,acl /dev/hdc1 /backup The /backup filesystem on the linux host was ext3, but you need to use additional mount options if you want to use extended attributes or ACLs, so I remounted my backup partition umount /backup So I tried this to copy data to the linux box ‘host’ /opt/local/bin/rsync -av -hard-links -acls -xattrs -e ssh /Volumes/Src also did not work. Backup-bouncer doesn’t class those things as ‘critical’, so I thought from a backup point of view, I’d leave them out. So I couldn’t use the crtimes or fileflags patches. That compiled fine on my Debian box, and I ended up copying it over the /usr/bin/rsync that I already had on the server. So that left me with compiling the normal rsync 3.0.5 from. This does not work, since those two extra patches require a bunch of OSX specific header files. I attempted to compile rsync on my Debian Lenny server using the same build technique the macports version uses (ie. rsync generally requires that the version of rsync at the destination end also understands your command line arguments. However, I can’t do that when transferring to a non-mac. For example, if I do the following, backup-bouncer’s verify tells me my ‘testdir’ passes all tests sudo /opt/local/bin/rsync -av -crtimes -hard-links -acls -xattrs -fileflags /Volumes/Src testdir Using the macports rsync, it is really good at rsyncing between two local directories or to a directory on another Mac. You then use your directory copying program to copy the test files elsewhere and then use backup-bouncer to check if all the OSX metadata were copied across. I also installed backup-bouncer which can create an OSX volume containing a set of test files, each with some of the more unusual features of OSX. Interestingly, it is v3.0.5 plus some additional patches for OSX (fileflags and crtimes patches). I ended up installing the latest version of rsync on my macbook using macports. Apparently, the more recent versions of rsync (latest is 3.0.6) include features that allow them to save/restore most of the OSX specific ‘metadata’. Obviously, if you’re copying a Mac directory elsewhere for backup purposes you’d like to be able to restore all your files plus this ‘extra metadata’.Īpparently the oldish version of rsync (v2.6.9 on my OSX 10.5.7) has the Apple specific -E special option to allow it to capture this extra ‘metadata’, but it only really works if you’re copying to another directory on the same server, or to another Mac running the same modded Apple rsync. Unlike most other Unix filesystems, the HFS+ filesystem that Macs use includes a bunch of extra ‘metadata’ such as resource forks, finder-flags, finder-locks, a special type of creation-date, bsd-flags etc. It’s often as simple as rsync -av -e ssh source_dir did I know, rsync to/from a Mac to a non-Mac unix is actually quite complicated. I’ve been using rsync for quite some time to backup directories between linux and other types of Unix systems. ![]() I never worked out how to get it to back up 100% of all the unusual metadata that MAC filesystems include, but it works well enough for my purposes. Warning The discussion below relates to my attempts to use rsync to back up a directory on a MAC to a directory on a remote linux host. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |