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


Click here to return to the 'Preserve resource forks during backups via tar and ftp' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Preserve resource forks during backups via tar and ftp
Authored by: jwbales on Aug 10, '05 11:14:36AM

You can (should) also use compression to save time/bandwidth/diskspace...

Old...
ftp> put "| tar cvpf - username" username_backup.tar
New...
ftp> put "| tar zcvpf - username" username_backup.tar


[ Reply to This | # ]
Preserve resource forks during backups via tar and ftp
Authored by: jwbales on Aug 10, '05 11:17:14AM

Sorry forgot the .gz extention....

New...
ftp> put "| tar zcvpf - username" username_backup.tar.gz


[ Reply to This | # ]
well...
Authored by: nick on Aug 10, '05 11:41:33AM

if you really want to save bandwidth, you shouldn't backup tars via ftp but use rsync or unison. rsyncX and unison both support resource forks.



[ Reply to This | # ]
But what about backups to non Mac servers
Authored by: ruaric on Aug 10, '05 06:16:45PM

The point of using a tar file is to save the resource fork within it even if you backup to a non MacOS X machine (i.e. even if you backup to Linux or Windows which don't support resource forks they are still saved within the tar).



[ Reply to This | # ]
But what about backups to non Mac servers
Authored by: peterneillewis on Aug 11, '05 03:54:43AM

I think you will find that rsync under Tiger will backup resources to a non-Mac, it saves the extended data (resources and meta data) to ._ files, probably in exactly the same way that they are stored in the tar file.

It's just a shame that rsync under Tiger is so broken that it cannot backup a decent sized home directory without crashing or locking up (the crash took about five minutes to find in the source code (hint flist_expand), but the lockup I haven't tracked down yet). Perhaps 10.4.3/4/5/6?



[ Reply to This | # ]