|
|
10.4: Avoid rsync errors during backup due to Spotlight
I recently started using rsnapsot to do rsync backups from one Tiger box to another. It provides incremental backups without using too much disk space by using hard links. Working great so far, and not difficult to set up.
I'm glad I read your hint, since I didn't know that I needed to send the -E swith to have rsync include resource forks. Since I haven't been using the -E swith, I haven't run into the problem you described... yet. My question - is there any need to turn off indexing on the source volume? Would turning off indexing on the backup volume (or directory) be sufficient?
10.4: Avoid rsync errors during backup due to Spotlight
Good hint, though I haven't had this problem. I have disabled indexing on my backup volume totally and permanently, anyway.
10.4: Avoid rsync errors during backup due to Spotlight
See this comment about rdiff not handling resource forks
10.4: Avoid rsync errors during backup due to Spotlight
I was using a custom made perl script to do essentially this same exact thing on my server. It's running every two hours on user home folders, providing snapshots of them should things go wrong. However, after letting this run for about a week, my server needed to be rebooted, and would not boot subsequently. I am nearly convinced that it's related to the snapshots and vast number of files, because after about two weeks of it being up and running snapshots, again it rebooted, never to come back up.
excessive snapshots
Thanks for that cautionary warning. |
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 |
|