Sabotage and Lack of Data Backup Sink Company
"... yes, I was a huge idiot, first and foremost.
It was the guy handling the IT (and, yes, the same guy who I caught stealing from the company, and who did a slash-and-burn on some servers on his way out) who made the choice to rely on RAID as the only backup mechanism for the SQL server. He had set up automated backups for the HTTP server which contains the PHP code, but, inscrutably [sic], had no backup system in place for the SQL data. The ironic thing here is that one of his hobbies was telling everybody how smart he was.
This doesn't excuse what happened, though: I should have taken a better look at what he'd left behind, and fixed all of the things that needed fixing."
| The JournalSpace.com blog|
JournalSpace.com sent the drives to DriveSavers, hoping that the data could be recovered, but it could not: "The data was simply gone. Overwritten." Ultimately JournalSpace.com's failure was because it put too much trust in the team members of its hosting company, San Jose-based Lagomorphics, and it didn't take enough of a first-hand vested interest in making sure that its assets were well protected. The JournalSpace.com folks take accountability for the company's downfall, as they admit on what is left of the company's homepage:
"But, 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 JournalSpace.com and JournalSpace.net domains are currently for sale on eBay--the auction already has 31 bids from 14 bidders with the current bid at $2,400. The auction ends in six days and "15% of the sale price will be donated to the Susan G. Komen For The Cure charity." As to JournalSpace .com users who lost all of their blog and journal entries when the drives were wiped, a blogger by the name of Adrew S. reports that at least some of the posts might be able to recovered by using cached versions of their pages on Google.