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


Click here to return to the 'resource forks still a problem' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
resource forks still a problem
Authored by: redjar on Oct 28, '03 01:30:55PM

Just a note... as touched upon above, this should work alright if you are just backing up data and always use extensions. However, if you are hoping to use it to make incremental snapshot images of your entire drive, it won't work.

I attempted this set up a while back with my PowerBook (I already use it to backup all our servers and it works great.)

However, I wanted to make an exact image, bootable and all using the above techniques. The resource fork prevented this unfortunately.

RsyncX crapped out with malloc errors. The native cp doesn't support resource forks. I found a cp that did support resource forks, but it didn't support hard links, psync doesn't have the advanced features of rsync.

If anyone knows of a way to do this (commercial app would be fine) please share. Remember, it must support hard linking to really be feasible.



[ Reply to This | # ]
resource forks still a problem
Authored by: newkid on Oct 28, '03 11:25:58PM

You are right and thanks to to mention it: this technique is only for data (software installers can be copied in some cases, like if they are inside a .dmg for example).

It is not intended for systems, but it will backup databases as long as you issue a stop database beforehand.

If you want to backup your system, you must boot from a separate partition and create a .dmg with disk copy or use dd to output the appropriate /dev in raw mode into a file.



[ Reply to This | # ]
psync
Authored by: SOX on Oct 29, '03 12:51:02PM

I use Psync instead of Rsync or RsyncX (damn malloc errors!). pysnc seems to work more stably and is HFS resource fork aware.

The drawback with psync is that unlike rsync it wont work across the network to a remote computer. You have to mount the computer's drive and in that case you may run into problems with root squashing if you are trying to transfer root owned files.

Psync does have a cute way of dealing with files owned by users that dont exist on the remote machine. that can also used to workaround the root-squash issue. One of its options removes places all the ownership and priviledge info into a single file, and in restore mode psync will read this file and assign the ownership and priveledges.

the cpio trick works with psync just as it does with rsync. Psync is a tad slower than rsync which is slower than rdiff-backup, but in my experience the slow step in backups is the cpio step not the psync step.



[ Reply to This | # ]
resource forks still a problem
Authored by: mazatty on Oct 30, '03 03:37:47AM

you might want to look at Carbon Copy Cloner

it can make bootable copies of drives. you can schedule copies. it can use psync to synchronize the source to the target. prefix and postfix scripts can be assigned.

if you want to get this hint working with bootable backups, Mike Bombich explains how to do what CCC does, take a look here



[ Reply to This | # ]
resource forks still a problem
Authored by: ramsperger on Nov 06, '03 07:40:23PM
If you are looking for a commerical app. to do back ups, I recommend Retrospect. I have successfully restored individual files and entire machines using it. It is made by Dantz

[ Reply to This | # ]
resource forks still a problem
Authored by: kd4ttc on Apr 17, '05 02:11:37PM

the pax utility will do hard links! Just discovered this a short while ago. See man pax for details.

Steve



[ Reply to This | # ]
pax will create hard links
Authored by: kd4ttc on Apr 17, '05 02:13:02PM

The pax utility will do hard links! Just discovered this a short while ago. See man pax for details.

Steve



[ Reply to This | # ]