Prev: Sparse Bundle
Next: Cross-platform e-mail text size problems
From: Tom Harrington on 20 Jun 2008 13:07
It looks like Mozy has fixed the problems they were having with resource
forks. I was one of the people who had problems with Mozy 1.0 not
backing up resource forks, but the new version 1.0.1 has fixed the
problem for me.

I guess they intended to support resource forks in 1.0, but there were
some bugs related to them. Since the previous discussion here I've been
sending them logs and configuration data, and trying out beta versions,
and it looks like things are working now.

It was necessary to force Mozy to re-scan my files before it picked up
on the resource forks. I did this by opening the configuration window,
unchecking everything, checking them again, and letting it run for a
while scanning files before saving the configuration again. I don't
know if everyone will need to do this or if it's specific to my system
for some reason. I'd suggest just using the new version first, and not
bothering with this step unless the problem persists.

I'd be interested to hear if 1.0.1 fixes the problem for other people
who had trouble with 1.0. If you've had the problem, you'll be able to
tell if it's fixed when the next backup runs-- the total number of files
needing backup will be more than you'd normally expect, and Mozy's log
file will have a lot of references to uploading "..namedfork/rsrc"
files. Plus of course, if you restore a test file which should have a
resource fork, it should be OK.

If it's not fixed for you-- contact Mozy's mac support group, I found
them to be very responsive and eager to fix the problem.

--
Tom "Tom" Harrington
Independent Mac OS X developer since 2002
http://www.atomicbird.com/
 | 
Pages: 1
Prev: Sparse Bundle
Next: Cross-platform e-mail text size problems