JournalSpace Data Loss: What Happened and Lessons for Bloggers
In January 2009, thousands of bloggers woke up to find their blogs gone for good. JournalSpace, a popular blog hosting service, lost its entire database and had no usable backup. The site shut down, and years of writing vanished overnight. It remains one of the clearest warnings for anyone who publishes online. Here’s what happened and how to make sure it never happens to your blog.

Quick answer: JournalSpace closed in early 2009 after its database was overwritten and data recovery firm DriveSavers found it unrecoverable. The company said the likely cause was sabotage by a former employee, and its only “backup” was a mirrored drive that copied the damage. The lesson: keep your own regular, off-site backups of any blog, even on hosted platforms.
Table of Contents
What happened to JournalSpace
- JournalSpace’s database was wiped and overwritten. The company said there was no hardware failure; both drives were working.
- Its storage used mirroring (RAID), which protects against a failed drive but faithfully copies deletions too. It wasn’t a real backup.
- DriveSavers reported the data was unrecoverable.
- JournalSpace said a disgruntled former team member, caught stealing from the company months earlier, may have sabotaged the servers, though a catastrophic OS failure was also possible.
- Users couldn’t even recover posts from the Internet Archive’s Wayback Machine, because the site’s robots.txt had blocked it.
Users gathered on refuge forums to rebuild what they could from browser caches and old emails.
Lessons for every blogger
1. Mirroring is not a backup
A real backup is a separate copy, stored elsewhere, with older versions you can roll back to.
2. Keep your own copy
Even on Blogger, WordPress.com, Medium or Substack, export your content regularly. Most platforms offer an export tool.
3. Back up off-site and automatically
For self-hosted WordPress, use a backup service or plugin that stores copies away from your server. Compare options in our WordPress backup services guide.
4. Own your domain
Your own domain lets you move to a new host or platform without losing your address and readers.
5. Limit access
The JournalSpace story also shows the risk of insiders with full access. Use separate accounts, least-privilege roles and two-factor authentication, and keep backups where one person can’t delete them all.
Backup checklist
- Daily automatic backups of files and database.
- At least one copy in a different location (cloud storage or a backup service).
- Monthly export of your posts as a second format.
- Test a restore a few times a year.
FAQ
Was JournalSpace data ever recovered?
No. The service shut down after data recovery failed.
Is RAID a backup?
No. RAID protects against drive failure but copies deletions and corruption instantly.
How often should I back up my blog?
Daily for active blogs, plus an extra backup before big updates.
Subscribe to our weekly tech newsletter
New tech guides, free tools and 2-minute fixes, once a week.
🎁 100 Tech Terms ebook comes free with every subscription.
Unsubscribe anytime. See our privacy policy.







Well, that was ultimately retarded. I used to have a JS account as a backup journal when I want to write something private to a different audience than my main journal. Now I don’t remember all the friends I have on that service and the ones that I do remember… I don’t know if they’ve even bother rejoining the service.
Guess I’ll be resurrecting another closed account from another online service instead of trying JournalSpace again. It’s a shame especially said account had the nicest journal layout of all my online journal accounts.
How could this ever happen to an established blog hosting operation? JournalSpace is really writing its name on history of the Internet.
that’s why you call data back up important, you should always have back ups of all your data, its a big loss when you really loss all your data
I think the site is back because I am seeing free blogs on it.
This is an aweful story with no winners. It does hilight the important of understanding the enemy within and accepting that this may come in the form at the hghest technical level. A system can only be protected from privilidged users by spreading redundancy accross not alone multiple systems but also multile agenies and individuals. Any system can be brought down by one person with access and informaton. It is therefore necessary to acept this and provide responsibility and power to rstore to multiple parties.
John
This is the second time I’ve had a blog/journal site crash on me. The last time was a hard drive with no possible recovery. The site never came back up. Journalspace seemed like a good place to start anew. It took me several months to re-enter all my poetry.
Yes people should be smarter and back up on a regular basis. But let’s face it, people aren’t. The previous journal site I used, one couldn’t even back up their journal without an email to the owner. And you’d be lucky to get the backup sent to you within a couple weeks. All in all it just sucks.
Frankly speaking I have never heard about JournalSpace blog, so it is hard to me to evaluate the situation.
I hate to say this, but this was absolutely avoidable.
When the main (or a senior) member of your IT staff leaves the company, you immediately perform a full check-over of your IT infrastructure. You make SURE that things are being backed up correctly, and that nothing untoward is going on, such as the member of staff leaving his usernames and passwords active.
This quote sums it up:- “A disgruntled member of the Lagomorphics team sabotaged some key servers several months ago after he was caught stealing from the company; as awful as the thought is, we cant rule out the possibility of additional sabotage”
In short terms…WHY? Why can’t you rule it out? Why weren’t all of his access and passwords revoked? Also, publicising this story (about the member of IT staff stealing) even further doesn’t cover up your incompetence, quite frankly. It makes your company look even worse. There is no scapegoat, here.
I have to say that I’ve never heard of JournalSpace, but if they can’t even take a backup of a couple of hard drives once a day (or, well…once, for that matter), it doesn’t surprise me that this has happened.
Here are some rules of backups
1. Backup all your data
2. Backup frequently
3. Take some backups off-site
4. Keep some old backups
5. Test your backups
6. Secure your backups
7. Perform integrity checking
via https://hardware.slashdot.org/comments.pl?sid=1078665&cid=26301511