"We’ve been working continuously throughout the weekend with the Cloud Files team to help ease the capacity constraints we previously discussed and restore full access to to Jungle Disk users of Cloud Files. Through our investigation we’ve determined that a significant cause of <i>the problem was a bug in Jungle Disk 2.60a that prevented the directory cache system from working properly</i> and resulted in an excessive load on the Cloud Files system even under normal operation. We have corrected the error and Jungle Disk 2.60c is now available for download."<p>Sounds like it <i>was</i> a Jungledisk problem, not a Mosso problem.
You need to back up to two or three services, all run by different organizations. Disk redundancy buys you little -- you need organizational redundancy. The chance of any particular service failing for business or technical reasons is much higher than the risk of disk failures.<p>Personally, I back Anybots up to:<p><pre><code> - a 3 TB ReadyNAS in the building (everything nightly)
- rsync.net (important stuff nightly)
- dropbox (important stuff instantly)
- USB drives I keep at home (mostly everything monthly)</code></pre>
Wow, this is most definitely quite an embarrassment for JungleDisk, transparency is nice, but doesn't offer much solace to those needing their files. Incidents like these are all one needs to convince themselves that switching to the cloud isn't reliable. Hopefully they'll be able to resolve the issue soon and save face.
Just like having one backup anywhere, it's not a reliable setup. Using multiple backups is always better, and frankly, easy. Just backup to JD and a few other services or even locally and you're good to go.<p>Personally, I'm working on setting up a local backup and backing <i>that</i> up to the cloud.
I was going to build a service based on cloudfiles over the weekend, but it was pretty much unusable, because I got timeouts all the time.<p>It was certainly disconcerting to see the failure of a component that was supposed to be the core of my infrastructure. Cloudfiles just moved out of beta about a week ago, and for growing pains the outage was pretty long.<p>According to their status updates, data integrity was never at stake, just availability. CDN files were always accessible.<p>I'm relieved to see that the Jungle Disk integration seems to be to blame for this, since this hints at a one-time peak load event rather than an overall infrastructure failure.<p>I think the ease of use of the CDN and low latency of delivery for many small files is a big win. Is anyone else here (thinking of) using them?
Looks like they're working hard to bring it back.<p><a href="http://status.cloudfiles.mosso.com/" rel="nofollow">http://status.cloudfiles.mosso.com/</a>
So, at the risk of asking a stupid question, does this mean the tag line on the front page ("Multiple datacenters to ensure high availability") is bunk?<p>I use S3, but not JD, so I don't keep up with it much. I thought that when they added Mosso, it was in case S3 went down -- am I misunderstanding how it works?