Mark Rasch, 2004-11-15
The fine print in an insurance policy becomes an issue when a bizarre chain of IT disasters leaves a company without a single copy of the source code to its flagship product.
Colapse all |
Post comment
The Worst Case Scenario
2004-11-16
Anonymous
Anonymous
I do not think the ruling is that wrong altho I think the motivation given is not a very good one.
The first issue here is that two weeks are ample time for creating a new offsite backup, and is also enough for disinfecting the laptop and restoring the sources on it.
The primary motivation for...
[ more ] [ reply ]
The first issue here is that two weeks are ample time for creating a new offsite backup, and is also enough for disinfecting the laptop and restoring the sources on it.
The primary motivation for...
[ more ] [ reply ]
The Worst Case Scenario
2004-11-16
Anonymous (1 replies)
Anonymous (1 replies)
How unfortunate that all of their softcopy backups were read/write and thus virus-vulnerable. If only there were a cheap, high-capacity, write-once data storage medium available! They could have copied their source to it and then put copies in one or more offsite locations. If it looked like a mu...
[ more ] [ reply ]
[ more ] [ reply ]
The Worst Case Scenario
2004-11-16
Anonymous
Anonymous
Hm. They deserved it. "Backup" on workstations and paper are not backup. The only real backup are full backups in to different fireprof bankboxes. The only backup kept onsite shold be the incremental backus also kept i the company safe. This is not worth much but it provides fast recovery of lost da...
[ more ] [ reply ]
[ more ] [ reply ]
The Worst Case Scenario
2004-11-16
Anonymous (1 replies)
Anonymous (1 replies)
The Worst Case Scenario
2004-11-17
Anonymous (2 replies)
Anonymous (2 replies)
They haven't ever backed up their source code to CD's? (or other removable mediums)
Or these CD's have been stolen too?...
[ more ] [ reply ]
Or these CD's have been stolen too?...
[ more ] [ reply ]
The Worst Case Scenario
2004-11-17
Anonymous
Anonymous
I think the company was scamming to get insurance money. There's no way a business built on a sole product of proprietary code is going to leave themselves so vulnerable.
And if they did, I have no sympathy. Even my 13 year old son knows to make backups of his homework onto a USB drive or flopp...
[ more ] [ reply ]
And if they did, I have no sympathy. Even my 13 year old son knows to make backups of his homework onto a USB drive or flopp...
[ more ] [ reply ]
The Worst Case Scenario
2004-11-18
Anonymous
Anonymous
I found it interesting to read that the company had its source code on four computers plus a paper copy. I suppose that it's quicker and more efficient to restore source code by hand than it is to restore it from an expensive, exotic and perhaps unreliable device such as a CD-R, thumb disk, or zip ...
[ more ] [ reply ]
[ more ] [ reply ]
human mistakes bite
2004-11-22
Anonymous (1 replies)
Anonymous (1 replies)
...but this doesn't mean that they "deserve it" or had it coming to them etc.
They made mistakes, EVERYONE will make a mistake at some point in time, several probably. I think the point of the article is that you want to better prepare yourself for these mistakes. Think about it, thats a pretty b...
[ more ] [ reply ]
They made mistakes, EVERYONE will make a mistake at some point in time, several probably. I think the point of the article is that you want to better prepare yourself for these mistakes. Think about it, thats a pretty b...
[ more ] [ reply ]
human mistakes bite
2004-11-24
Anonymous
Anonymous
I think the point is that a good backup plan is fairly obvious, yet they did not take that route. The decided a paper copy, an off site backup (on a server of some kind, it looks like), and an onsite backup (only on HDDs) was a viable plan.
Disaster recovery is the issue. It sounds like they ha...
[ more ] [ reply ]
Disaster recovery is the issue. It sounds like they ha...
[ more ] [ reply ]
And what the company was doing for these two weeks???...
[ more ] [ reply ]