|
|
A script to prevent damage from rm -rf malware
OK, so shadowmirror will not work across Volumes. I am looking for a relatively transparent way to mirror my User directory to another Volume. (A networked Windows file server via SMB or AFP, if it matters.) I am already duplicating the drive locally every night to another drive in my MDD G4 with CCC, but that might not help much if my office gets flooded again. (Long story....)
Anyway, which of the above —
RE: Network backup question
I think that all 3 meet your criteria, but rsync and rdiff-backup are going to be easier to use and understand.
remote backup
rsync, rdiff, and cpio all have a problem with HFS+ and that is resource forks and metadata are destroyed. For 99% of your osx files this makes no difference but you will end up regretting it eventually. macosxlabs' RsyncX instead of the built in rsync takes care of HFS+, but is like rysnc plagued with silent malloc failures on deep directory trees that make it unsuited for unattended usage. If you actually check your error logs to notice those sorts of failures then RsyncX is probably the single best solution.
remote backup
note that while cpio has problems with meta data, oddly enough this is not a problem for the prescribed usage of making hard links. this only affects the primary copy. that is dont use CPIO to make a backup copy. use it to make a hardlink image. make the bakcup copy with something else.
remote backup
Hmmm. Perhaps I will have the backup performed to my other Mac with an HFS+ volume, and make .dmg's of that volume from time to time.
remote backup
still will lose the creator code if the suffix is missing.
remote backup
According to this post, the metadata problem has been solved in recent versions of rdiff-backup.
That's been my experience so far as well. I haven't had a problem with my backups, having checked the logs. ---
RE: Network backup question
2nd note: Let me reiterate again, trying to store UNIX files on a windows file server is a disaster waiting to happen if you are trying to make a completely recoverable file. The best way to do this would be to make a tar backup (or a dmg image or something like it) and save that file on the windows server. Permissions and such will be lost in a file copy style backup (like rsync, rdiff, etc.) and if you're only wanting to backup document files and such, that's not going to be a problem. A full restore, however, would be messed up beyond belief.
RE: Network backup question
the native Tar and zip are not hfs aware either. however, you can use the new apple zip-archive feature and transport that. (dont expand it on the remote file system or you may lose the meta data) |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysNo new commentsLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.09 seconds |
|