I was just reading a post on Data Center Knowledge this morning about a blog hosting service that I had actually heard of, Journalspace, who is apparently shutting their doors after they apparently lost all of their clients data due to one of the poorest backup strategies I have every heard of. This is yet another glowing, bright red & blinking example as to why you get what you pay for with your hosting provider, in my opinion.
At Pleth, we have one of the most comprehensive offsite backup solutions on the market. Of course by making this offering a part of our base managed hosting solution we are forced to relay those costs onto our clients, but as you will see below, this peace of mind is hard to put a price tag on. If you don’t believe me, just ask some of the Journalspace clients that are staring at the daunting task of starting all over again in 2009. I wouldn’t be surprised to hear about some lawsuits over this in the next year…
Here’s an excerpt of the article on Data Center Knowledge:
Also, if any Journalspace clients out there that would like to discuss webhosting for their blogs on a safe, redundant, secure, and reliable hosting platform, please drop us a note.
The blog hosting service Journalspace is shutting down after all its user data was lost. Rather than backing up its data at another location, Journalspace mirrored the data on a separate drive on the same server. When the data on both drives went missing, the service apparently had no backups it could use to restore the data.
“There was no hardware failure,” reads the notice to users. “Both drives are operating fine. The data was simply gone. Overwritten. … Clearly, we failed to take the steps to prevent this from happening. And for that we are very sorry. So, after nearly six years, journalspace is no more.”
The site had a rank of 106,000 on Alexa, suggesting some meaningful traffic. Obviously, a cautionary tale about back and recovery practices. See Slashdot for more discussion.
Data Loss Dooms Blog Hosting Service « Data Center Knowledge
Questions or Comments?