<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Mozy Woes on Mac</title>
	<atom:link href="http://thesmithfam.org/blog/2009/09/04/mozy-woes-on-mac/feed/" rel="self" type="application/rss+xml" />
	<link>http://thesmithfam.org/blog/2009/09/04/mozy-woes-on-mac/</link>
	<description>Your blog is probably better than mine.</description>
	<lastBuildDate>Tue, 07 Sep 2010 02:05:02 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Dave</title>
		<link>http://thesmithfam.org/blog/2009/09/04/mozy-woes-on-mac/comment-page-2/#comment-103081</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Wed, 16 Jun 2010 02:16:49 +0000</pubDate>
		<guid isPermaLink="false">http://thesmithfam.org/blog/?p=310#comment-103081</guid>
		<description>i am VERY impressed with CrashPlan on the Mac. They do something fundamentally different from Mozy, and it makes a big difference. For example, they collect the list of modified files as they are modified. That way, when backup time comes, they don&#039;t have to spend 3 hours building the list of files to backup -- the list is already built, and ready to go. Incremental bckups complete in minutes rather than hours. 

It&#039;s so fast that I let it back me up every 30 minutes, and I&#039;ve never noticed any CPU hogging or memory hogging.

They have a great UI, and restores are a real piece of cake compared to Mozy. Browsing for backup files to restore is nice and snappy.

Go CrashPlan!</description>
		<content:encoded><![CDATA[<p>i am VERY impressed with CrashPlan on the Mac. They do something fundamentally different from Mozy, and it makes a big difference. For example, they collect the list of modified files as they are modified. That way, when backup time comes, they don&#8217;t have to spend 3 hours building the list of files to backup &#8212; the list is already built, and ready to go. Incremental bckups complete in minutes rather than hours. </p>
<p>It&#8217;s so fast that I let it back me up every 30 minutes, and I&#8217;ve never noticed any CPU hogging or memory hogging.</p>
<p>They have a great UI, and restores are a real piece of cake compared to Mozy. Browsing for backup files to restore is nice and snappy.</p>
<p>Go CrashPlan!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sean</title>
		<link>http://thesmithfam.org/blog/2009/09/04/mozy-woes-on-mac/comment-page-2/#comment-100500</link>
		<dc:creator>Sean</dc:creator>
		<pubDate>Sat, 27 Mar 2010 15:44:57 +0000</pubDate>
		<guid isPermaLink="false">http://thesmithfam.org/blog/?p=310#comment-100500</guid>
		<description>Is Dan Reese still on this site?

I am running Mozy 1.7.1 (51675) on a PPC G4 Mac running Tiger 10.4.11.

I keep getting disconnected, over and over again. Here are some extracts from the log file:

Any suggestions?


2010-03-26 17:08:53.717 MozyHomeBackup[387:622b] INF (send) NSCFInputStream error: NSError &quot;POSIX error: Operation timed out&quot; Domain=NSPOSIXErrorDomain Code=60
2010-03-26 17:08:53.717 MozyHomeBackup[387:622b] INF (send) Disconnecting
2010-03-26 17:08:53.727 MozyHomeBackup[387:622b] INF (send) Batch failed: Unable to connect to backup servers (0x80000001 - ConnectionError1)
2010-03-26 17:14:29.411 MozyHomeBackup[387:622b] INF (send) Offering 486 files (0 are removes)
2010-03-26 17:14:29.522 MozyHomeBackup[387:622b] INF (send) Connecting to r4165.mozy.data.ut3.berkeleydata.com (74.112.149.130)
2010-03-26 17:14:30.997 MozyHomeBackup[387:622b] INF (send) Server version is 1.5.0.40

2010-03-26 17:15:58.479 MozyHomeBackup[387:622b] INF (send) NSCFInputStream error: NSError &quot;POSIX error: Operation timed out&quot; Domain=NSPOSIXErrorDomain Code=60
2010-03-26 17:15:58.479 MozyHomeBackup[387:622b] INF (send) Disconnecting
2010-03-26 17:15:58.481 MozyHomeBackup[387:622b] INF (send) Batch failed: Unable to connect to backup servers (0x80000001 - ConnectionError1)
2010-03-26 17:22:14.366 MozyHomeBackup[387:622b] INF (send) Offering 486 files (0 are removes)
2010-03-26 17:22:14.487 MozyHomeBackup[387:622b] INF (send) Connecting to r4165.mozy.data.ut3.berkeleydata.com (74.112.149.130)
2010-03-26 17:22:15.989 MozyHomeBackup[387:622b] INF (send) Server version is 1.5.0.40


2010-03-26 17:23:38.518 MozyHomeBackup[387:622b] INF (send) NSCFInputStream error: NSError &quot;POSIX error: Operation timed out&quot; Domain=NSPOSIXErrorDomain Code=60
2010-03-26 17:23:38.518 MozyHomeBackup[387:622b] INF (send) Disconnecting
2010-03-26 17:23:38.528 MozyHomeBackup[387:622b] INF (send) Batch failed: Unable to connect to backup servers (0x80000001 - ConnectionError1)
2010-03-26 17:30:28.850 MozyHomeBackup[387:622b] INF (send) Offering 486 files (0 are removes)
2010-03-26 17:30:29.072 MozyHomeBackup[387:622b] INF (send) Connecting to r4165.mozy.data.ut3.berkeleydata.com (74.112.149.130)
2010-03-26 17:30:30.607 MozyHomeBackup[387:622b] INF (send) Server version is 1.5.0.40


2010-03-26 17:33:10.090 MozyHomeBackup[387:622b] INF (send) NSCFInputStream error: NSError &quot;POSIX error: Operation timed out&quot; Domain=NSPOSIXErrorDomain Code=60
2010-03-26 17:33:10.090 MozyHomeBackup[387:622b] INF (send) Disconnecting
2010-03-26 17:33:10.100 MozyHomeBackup[387:622b] INF (send) Batch failed: Unable to connect to backup servers (0x80000001 - ConnectionError1)
2010-03-26 17:40:35.644 MozyHomeBackup[387:622b] INF (send) Offering 486 files (0 are removes)
2010-03-26 17:40:35.711 MozyHomeBackup[387:622b] INF (send) Connecting to r4165.mozy.data.ut3.berkeleydata.com (74.112.149.130)
2010-03-26 17:40:37.314 MozyHomeBackup[387:622b] INF (send) Server version is 1.5.0.40


2010-03-26 17:43:14.639 MozyHomeBackup[387:622b] INF (send) NSCFInputStream error: NSError &quot;POSIX error: Operation timed out&quot; Domain=NSPOSIXErrorDomain Code=60
2010-03-26 17:43:14.640 MozyHomeBackup[387:622b] INF (send) Disconnecting
2010-03-26 17:43:14.657 MozyHomeBackup[387:622b] INF (send) Batch failed: Unable to connect to backup servers (0x80000001 - ConnectionError1)

2010-03-26 17:48:49.823 MozyHomeBackup[387:622b] INF (send) NSCFInputStream error: NSError &quot;POSIX error: Operation timed out&quot; Domain=NSPOSIXErrorDomain Code=60
2010-03-26 17:48:49.824 MozyHomeBackup[387:622b] INF (send) Disconnecting
2010-03-26 17:48:49.833 MozyHomeBackup[387:622b] INF (send) Batch failed: Unable to connect to backup servers (0x80000001 - ConnectionError1)
2010-03-26 17:50:26.538 MozyHomeBackup[387:622b] INF (send) Offering 502 files (0 are removes)
2010-03-26 17:50:26.571 MozyHomeBackup[387:622b] INF (send) Connecting to r4165.mozy.data.ut3.berkeleydata.com (74.112.149.130)
2010-03-26 17:50:28.053 MozyHomeBackup[387:622b] INF (send) Server version is 1.5.0.40

2010-03-26 17:51:54.752 MozyHomeBackup[387:622b] INF (send) NSCFInputStream error: NSError &quot;POSIX error: Operation timed out&quot; Domain=NSPOSIXErrorDomain Code=60
2010-03-26 17:51:54.753 MozyHomeBackup[387:622b] INF (send) Disconnecting
2010-03-26 17:51:54.764 MozyHomeBackup[387:622b] INF (send) Batch failed: Unable to connect to backup servers (0x80000001 - ConnectionError1)</description>
		<content:encoded><![CDATA[<p>Is Dan Reese still on this site?</p>
<p>I am running Mozy 1.7.1 (51675) on a PPC G4 Mac running Tiger 10.4.11.</p>
<p>I keep getting disconnected, over and over again. Here are some extracts from the log file:</p>
<p>Any suggestions?</p>
<p>2010-03-26 17:08:53.717 MozyHomeBackup[387:622b] INF (send) NSCFInputStream error: NSError &#8220;POSIX error: Operation timed out&#8221; Domain=NSPOSIXErrorDomain Code=60<br />
2010-03-26 17:08:53.717 MozyHomeBackup[387:622b] INF (send) Disconnecting<br />
2010-03-26 17:08:53.727 MozyHomeBackup[387:622b] INF (send) Batch failed: Unable to connect to backup servers (0&#215;80000001 &#8211; ConnectionError1)<br />
2010-03-26 17:14:29.411 MozyHomeBackup[387:622b] INF (send) Offering 486 files (0 are removes)<br />
2010-03-26 17:14:29.522 MozyHomeBackup[387:622b] INF (send) Connecting to r4165.mozy.data.ut3.berkeleydata.com (74.112.149.130)<br />
2010-03-26 17:14:30.997 MozyHomeBackup[387:622b] INF (send) Server version is 1.5.0.40</p>
<p>2010-03-26 17:15:58.479 MozyHomeBackup[387:622b] INF (send) NSCFInputStream error: NSError &#8220;POSIX error: Operation timed out&#8221; Domain=NSPOSIXErrorDomain Code=60<br />
2010-03-26 17:15:58.479 MozyHomeBackup[387:622b] INF (send) Disconnecting<br />
2010-03-26 17:15:58.481 MozyHomeBackup[387:622b] INF (send) Batch failed: Unable to connect to backup servers (0&#215;80000001 &#8211; ConnectionError1)<br />
2010-03-26 17:22:14.366 MozyHomeBackup[387:622b] INF (send) Offering 486 files (0 are removes)<br />
2010-03-26 17:22:14.487 MozyHomeBackup[387:622b] INF (send) Connecting to r4165.mozy.data.ut3.berkeleydata.com (74.112.149.130)<br />
2010-03-26 17:22:15.989 MozyHomeBackup[387:622b] INF (send) Server version is 1.5.0.40</p>
<p>2010-03-26 17:23:38.518 MozyHomeBackup[387:622b] INF (send) NSCFInputStream error: NSError &#8220;POSIX error: Operation timed out&#8221; Domain=NSPOSIXErrorDomain Code=60<br />
2010-03-26 17:23:38.518 MozyHomeBackup[387:622b] INF (send) Disconnecting<br />
2010-03-26 17:23:38.528 MozyHomeBackup[387:622b] INF (send) Batch failed: Unable to connect to backup servers (0&#215;80000001 &#8211; ConnectionError1)<br />
2010-03-26 17:30:28.850 MozyHomeBackup[387:622b] INF (send) Offering 486 files (0 are removes)<br />
2010-03-26 17:30:29.072 MozyHomeBackup[387:622b] INF (send) Connecting to r4165.mozy.data.ut3.berkeleydata.com (74.112.149.130)<br />
2010-03-26 17:30:30.607 MozyHomeBackup[387:622b] INF (send) Server version is 1.5.0.40</p>
<p>2010-03-26 17:33:10.090 MozyHomeBackup[387:622b] INF (send) NSCFInputStream error: NSError &#8220;POSIX error: Operation timed out&#8221; Domain=NSPOSIXErrorDomain Code=60<br />
2010-03-26 17:33:10.090 MozyHomeBackup[387:622b] INF (send) Disconnecting<br />
2010-03-26 17:33:10.100 MozyHomeBackup[387:622b] INF (send) Batch failed: Unable to connect to backup servers (0&#215;80000001 &#8211; ConnectionError1)<br />
2010-03-26 17:40:35.644 MozyHomeBackup[387:622b] INF (send) Offering 486 files (0 are removes)<br />
2010-03-26 17:40:35.711 MozyHomeBackup[387:622b] INF (send) Connecting to r4165.mozy.data.ut3.berkeleydata.com (74.112.149.130)<br />
2010-03-26 17:40:37.314 MozyHomeBackup[387:622b] INF (send) Server version is 1.5.0.40</p>
<p>2010-03-26 17:43:14.639 MozyHomeBackup[387:622b] INF (send) NSCFInputStream error: NSError &#8220;POSIX error: Operation timed out&#8221; Domain=NSPOSIXErrorDomain Code=60<br />
2010-03-26 17:43:14.640 MozyHomeBackup[387:622b] INF (send) Disconnecting<br />
2010-03-26 17:43:14.657 MozyHomeBackup[387:622b] INF (send) Batch failed: Unable to connect to backup servers (0&#215;80000001 &#8211; ConnectionError1)</p>
<p>2010-03-26 17:48:49.823 MozyHomeBackup[387:622b] INF (send) NSCFInputStream error: NSError &#8220;POSIX error: Operation timed out&#8221; Domain=NSPOSIXErrorDomain Code=60<br />
2010-03-26 17:48:49.824 MozyHomeBackup[387:622b] INF (send) Disconnecting<br />
2010-03-26 17:48:49.833 MozyHomeBackup[387:622b] INF (send) Batch failed: Unable to connect to backup servers (0&#215;80000001 &#8211; ConnectionError1)<br />
2010-03-26 17:50:26.538 MozyHomeBackup[387:622b] INF (send) Offering 502 files (0 are removes)<br />
2010-03-26 17:50:26.571 MozyHomeBackup[387:622b] INF (send) Connecting to r4165.mozy.data.ut3.berkeleydata.com (74.112.149.130)<br />
2010-03-26 17:50:28.053 MozyHomeBackup[387:622b] INF (send) Server version is 1.5.0.40</p>
<p>2010-03-26 17:51:54.752 MozyHomeBackup[387:622b] INF (send) NSCFInputStream error: NSError &#8220;POSIX error: Operation timed out&#8221; Domain=NSPOSIXErrorDomain Code=60<br />
2010-03-26 17:51:54.753 MozyHomeBackup[387:622b] INF (send) Disconnecting<br />
2010-03-26 17:51:54.764 MozyHomeBackup[387:622b] INF (send) Batch failed: Unable to connect to backup servers (0&#215;80000001 &#8211; ConnectionError1)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lawrence</title>
		<link>http://thesmithfam.org/blog/2009/09/04/mozy-woes-on-mac/comment-page-2/#comment-100494</link>
		<dc:creator>Lawrence</dc:creator>
		<pubDate>Sat, 27 Mar 2010 13:44:43 +0000</pubDate>
		<guid isPermaLink="false">http://thesmithfam.org/blog/?p=310#comment-100494</guid>
		<description>Guys, forget Mozy.
I&#039;ve been using the paid version of CrashPlan since January, I&#039;ve had one issue which was promptly solved.
CrashPlan also allows you to backup over the internet to a friend&#039;s computer (you don&#039;t have to pay for that).</description>
		<content:encoded><![CDATA[<p>Guys, forget Mozy.<br />
I&#8217;ve been using the paid version of CrashPlan since January, I&#8217;ve had one issue which was promptly solved.<br />
CrashPlan also allows you to backup over the internet to a friend&#8217;s computer (you don&#8217;t have to pay for that).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark</title>
		<link>http://thesmithfam.org/blog/2009/09/04/mozy-woes-on-mac/comment-page-2/#comment-100368</link>
		<dc:creator>Mark</dc:creator>
		<pubDate>Wed, 24 Mar 2010 23:17:29 +0000</pubDate>
		<guid isPermaLink="false">http://thesmithfam.org/blog/?p=310#comment-100368</guid>
		<description>Oddly, I had exactly the opposite problem... 1.6 was the only release in the past 6 months or so that worked well, then it stopped and I&#039;d get either a connection error or clienterror3.  They told me to update to 1.7, which i haven&#039;t been able to get to work at all.  They think it&#039;s a Snow Leopard problem and have asked me to downgrade back to 1.6.  They do seem very enthusiastic about fixing things, I just wish they had fewer things to fix.  Oh, and a faster upload would be nice.  I&#039;ve never actually had a full backup... it would take months.  :-)</description>
		<content:encoded><![CDATA[<p>Oddly, I had exactly the opposite problem&#8230; 1.6 was the only release in the past 6 months or so that worked well, then it stopped and I&#8217;d get either a connection error or clienterror3.  They told me to update to 1.7, which i haven&#8217;t been able to get to work at all.  They think it&#8217;s a Snow Leopard problem and have asked me to downgrade back to 1.6.  They do seem very enthusiastic about fixing things, I just wish they had fewer things to fix.  Oh, and a faster upload would be nice.  I&#8217;ve never actually had a full backup&#8230; it would take months.  :-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave</title>
		<link>http://thesmithfam.org/blog/2009/09/04/mozy-woes-on-mac/comment-page-2/#comment-100223</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Sun, 21 Mar 2010 18:32:07 +0000</pubDate>
		<guid isPermaLink="false">http://thesmithfam.org/blog/?p=310#comment-100223</guid>
		<description>Mozy 1.7 seems to be working much better. Backups complete in about 1/4th of the time as 1.6. Unfortunately, the MozyHomeBackup process is using 1GB of my 4GB of RAM, even when idle. Any ideas on that? I have debug messages disabled.</description>
		<content:encoded><![CDATA[<p>Mozy 1.7 seems to be working much better. Backups complete in about 1/4th of the time as 1.6. Unfortunately, the MozyHomeBackup process is using 1GB of my 4GB of RAM, even when idle. Any ideas on that? I have debug messages disabled.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rooskie</title>
		<link>http://thesmithfam.org/blog/2009/09/04/mozy-woes-on-mac/comment-page-2/#comment-99859</link>
		<dc:creator>Rooskie</dc:creator>
		<pubDate>Sun, 14 Mar 2010 08:19:40 +0000</pubDate>
		<guid isPermaLink="false">http://thesmithfam.org/blog/?p=310#comment-99859</guid>
		<description>Mozy is a poor choice for mac users: HOGGS resources, CPU over heating - fans kick on to high gear. I&#039;m uninstalling immediately. After trying to do a back up 5 times and waiting hrs at a time to have only transferred 5 Gig.

Good luck!</description>
		<content:encoded><![CDATA[<p>Mozy is a poor choice for mac users: HOGGS resources, CPU over heating &#8211; fans kick on to high gear. I&#8217;m uninstalling immediately. After trying to do a back up 5 times and waiting hrs at a time to have only transferred 5 Gig.</p>
<p>Good luck!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mel</title>
		<link>http://thesmithfam.org/blog/2009/09/04/mozy-woes-on-mac/comment-page-2/#comment-99706</link>
		<dc:creator>Mel</dc:creator>
		<pubDate>Thu, 11 Mar 2010 06:19:51 +0000</pubDate>
		<guid isPermaLink="false">http://thesmithfam.org/blog/?p=310#comment-99706</guid>
		<description>I just got purchased this product over a week ago for my mac as I have most of my important files on a USB mounted drive. I&#039;m still working with support to get this to work! I havent been able to get backup working as it scans my drives and does nothing...
Pretty frustrating. I am running on 10.5.8. I myself work as an IT engineer. Logging on this is terrible. It doesn&#039;t tell you much. Crash reports will give you something. Is there a debug mode on this?
I need a work around. If not, I want my money back.</description>
		<content:encoded><![CDATA[<p>I just got purchased this product over a week ago for my mac as I have most of my important files on a USB mounted drive. I&#8217;m still working with support to get this to work! I havent been able to get backup working as it scans my drives and does nothing&#8230;<br />
Pretty frustrating. I am running on 10.5.8. I myself work as an IT engineer. Logging on this is terrible. It doesn&#8217;t tell you much. Crash reports will give you something. Is there a debug mode on this?<br />
I need a work around. If not, I want my money back.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave</title>
		<link>http://thesmithfam.org/blog/2009/09/04/mozy-woes-on-mac/comment-page-2/#comment-99140</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Sat, 27 Feb 2010 19:15:52 +0000</pubDate>
		<guid isPermaLink="false">http://thesmithfam.org/blog/?p=310#comment-99140</guid>
		<description>I sent a support email to Mozy, and after some back-and-forth, it got escalated to another technician. I never heard from him, but now the problem appears to be solved. My backups are running smoothly now and my files appear correctly for restore in the web app.

Thanks Mozy!

P.S. To encourage smooth operation, I upgraded my iMac from 2GB to 4GB of RAM, and now things are much better.</description>
		<content:encoded><![CDATA[<p>I sent a support email to Mozy, and after some back-and-forth, it got escalated to another technician. I never heard from him, but now the problem appears to be solved. My backups are running smoothly now and my files appear correctly for restore in the web app.</p>
<p>Thanks Mozy!</p>
<p>P.S. To encourage smooth operation, I upgraded my iMac from 2GB to 4GB of RAM, and now things are much better.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lee</title>
		<link>http://thesmithfam.org/blog/2009/09/04/mozy-woes-on-mac/comment-page-2/#comment-99009</link>
		<dc:creator>Lee</dc:creator>
		<pubDate>Thu, 25 Feb 2010 18:21:34 +0000</pubDate>
		<guid isPermaLink="false">http://thesmithfam.org/blog/?p=310#comment-99009</guid>
		<description>Same problems with Mozy explained here. Especially bad issues with processor and memory usage (the app wouldn&#039;t let go of nearly 1.5GB RAM and over 2GB virtual memory, even when it was idle). I had around 32 GB backed up with Mozy, they said that my woes could have had something to do with that. I worked with Mozy tech support on this over the course of more than a month. They had me downgrade to the previous release, then, when it came out, upgrade to the latest release. All to no avail. I canceled my subscription and they refunded me 5 months. (the problems started back in October and they had a record of that in their ticketing system). Giving Jungle Disk a whirl. Good luck everyone!</description>
		<content:encoded><![CDATA[<p>Same problems with Mozy explained here. Especially bad issues with processor and memory usage (the app wouldn&#8217;t let go of nearly 1.5GB RAM and over 2GB virtual memory, even when it was idle). I had around 32 GB backed up with Mozy, they said that my woes could have had something to do with that. I worked with Mozy tech support on this over the course of more than a month. They had me downgrade to the previous release, then, when it came out, upgrade to the latest release. All to no avail. I canceled my subscription and they refunded me 5 months. (the problems started back in October and they had a record of that in their ticketing system). Giving Jungle Disk a whirl. Good luck everyone!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Terry</title>
		<link>http://thesmithfam.org/blog/2009/09/04/mozy-woes-on-mac/comment-page-2/#comment-98977</link>
		<dc:creator>Terry</dc:creator>
		<pubDate>Thu, 25 Feb 2010 01:07:42 +0000</pubDate>
		<guid isPermaLink="false">http://thesmithfam.org/blog/?p=310#comment-98977</guid>
		<description>Unfortunately, Dave, I see the same thing.  The Mozy backup service isn&#039;t working for me.  With the latest Snow Leopard OS X 10.6.2 and Mozy 1.6.2.50103, repaired permissions and verified disk structure, I see in the log: Preparing 0 files (0 bytes)

I&#039;ve removed every Mozy, rebooted, reinstalled, and the same thing happens.  Going into MozyHome also shows weird results in terms of my BackupSet sizes, with a summary of &quot;No files selected for Backup&quot; - despite the fact that I have correctly defined that 50 GB should be backed up.</description>
		<content:encoded><![CDATA[<p>Unfortunately, Dave, I see the same thing.  The Mozy backup service isn&#8217;t working for me.  With the latest Snow Leopard OS X 10.6.2 and Mozy 1.6.2.50103, repaired permissions and verified disk structure, I see in the log: Preparing 0 files (0 bytes)</p>
<p>I&#8217;ve removed every Mozy, rebooted, reinstalled, and the same thing happens.  Going into MozyHome also shows weird results in terms of my BackupSet sizes, with a summary of &#8220;No files selected for Backup&#8221; &#8211; despite the fact that I have correctly defined that 50 GB should be backed up.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
