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


Click here to return to the '10.4: Avoid rsync errors during backup due to Spotlight' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.4: Avoid rsync errors during backup due to Spotlight
Authored by: CaptainQueeg on Nov 09, '05 08:39:30AM
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?

[ Reply to This | # ]

10.4: Avoid rsync errors during backup due to Spotlight
Authored by: murali1080 on Nov 09, '05 01:05:58PM

Good hint, though I haven't had this problem. I have disabled indexing on my backup volume totally and permanently, anyway.

Also try rdiff-backup. Its in someways better and more mature than rsnapshot. The stable version is comparable to professional backup tools. I also like rsnapshot but do not use it anymore.



[ Reply to This | # ]
10.4: Avoid rsync errors during backup due to Spotlight
Authored by: ptone on Nov 11, '05 06:31:21AM
See this comment about rdiff not handling resource forks

[ Reply to This | # ]
10.4: Avoid rsync errors during backup due to Spotlight
Authored by: fragerybou on Nov 09, '05 03:22:42PM

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.

Be careful of how often you run snapshot backups, and how many files it will end up creating, especially on a boot volume.



[ Reply to This | # ]
excessive snapshots
Authored by: sjk on Nov 10, '05 12:18:44PM

Thanks for that cautionary warning.



[ Reply to This | # ]