Mozy has released an update to their MacMozy software, bringing it to version 0.8.0.0. The update was released Oct. 25th and I’ve been running it for a little over a week. I updated both the free account to back up my MacBook along with the unlimited account to backup my main iMac.
While I hadn’t had any problems since updated to Leopard (MacMozy 0.7.0.0 or higher is needed for Leopard) I immediately started getting ConnectionError1 during my first backups after upgrading on my iMac. (My MacBook backups are small and I may just not have done enough to get it there). This is a known issue with a temporary work around of opening port 443 for outbound connections in the firewall. I hadn’t needed to do anything Mozy related with the Leopard firewall since upgrading to Leopard. Besides, the Leopard firewall doesn’t provide a way (through the preferences) to manage ports, rather it wants to manage apps. I added Mozy to the list of applications to allow incoming connections (click the thumbnail to the right). This seemed to resolve the problem as the error did not occur since the change. Still, I’m skeptical that it was a fix and not coincidence. The Mozy work around dealt with outbound connections being blocked and according to the setting I opened Mozy up for inbound connections. I’ll add it to my list of questions about the firewall.
I recently downloaded a iso image of the latest Fedora release which was 3.3 GB. Normally I wouldn’t bother backing this up since I could just download it again and it would take the better part of a day to back it up with my Internet connection. But I decided this would be a good test for Mozy and told Mozy to back it up. I typically throttle bandwidth to about 75% of the connection (Comcast seems to dislike full-out usage for extended lengths of time so I find I get better overall results by throttling) but I removed the throttle for this test. Mozy did consistently use over 90% of my upload speed, which may have been all Comcast was willing to give it.
Just like every other upgrade I restored a few files and made sure they’re still valid. I pull some down that were backed up with older versions (I just pick a file from the oldest backup set) and some that were just backed up with the new versions. I didn’t find any problems.
The list of fixes from the release notes includes:
* improved update check logic
* fixed web links for some server errors
* added os version, architecture and memory size to log output
* automatic backup idle time setting can now be set to zero
* added change log notes to readme file
* only wait 10 minutes for response before retrying
* throttling measurements now match activity monitor
* added definition of “back up” to readme file
* added uninstall option in status drop-down menu
* changed default backup schedule to once daily
* backup set editor UI improvements
* status app can now be run by multiple users at the same time
* added readme file to disk image
* fixed waiting forever to write data
* updated quick start guide
* added known issues to readme file
* fixed ical backup set for leopard
The last item is related to iCal backup sets in Leopard. I’ve noticed that with this version both the “iCal” and “Keychains” backup sets search forever (at least as long as I’m willing to wait) on the configuration screen and don’t find any files. I also backup these items by selecting them in the “Files and Folders” configurations which may be why I haven’t had a problem. I’m not sure this is really fixed. I hadn’t noticed this problem under 0.7.
I hadn’t seen the “waiting forever to write data” in the 0.7 release but had encountered it earlier. The throttling change confused me at first as I thought they had limited choices. It had been Kbps which matched how my ISP rated the connection. This time I went in and saw 96KBps as the choice just below no throttling. They switched from bits to Bytes so it now matches activity monitor, and iStats Menu for that matter.
The new feature to “set the automatic backup idle time” to zero means a backup will be done every two hours, even if you’re using the Mac. Mozy will only do an automatic backup every two hours, so setting the idle to zero means it will kick off when that timer expires. This is good for my laptop which is rarely idle. This way it will get at least one backup per session.
The known issues that have been identified by Mozy are:
* Mozy does not fully support bundles.
* Mozy does not back up resource forks or symbolic links.
* Occasionally, Mozy has trouble communicating with our servers (ConnectionError1). If you have a firewall, please allow Mozy to make outbound connections on port 443. If not, please wait a few minutes and then restart the backup process.
Even though Mozy is still in beta for the Mac it’s been awhile since I’ve had any serious problems with it. I’m obviously a big fan of Mozy and have trusted by own backups to it (although not my only backup). One reason I’m a fan is they offer a free account with 2GB of storage so there’s no risk. I used this for months before deciding to commit to the unlimited account. You can go to Mozy’s website to get a free 2GB account (aff) and use referral code E62DWM to get both of us an extra 256MB of storage. They’ve redesigned their site and made the free account a bit harder to find. Select MozyHome from the main page the look for “MozyHome Free”