For novel ideas about building embedded systems (both hardware and firmware), join the 40,000+ engineers who subscribe to The Embedded Muse, a free biweekly newsletter. The Muse has no hype and no vendor PR. Click here to subscribe.

By Jack Ganssle

Hurricane Season

Published 6/01/2009

It's hurricane season in the US. Do you know where your data is?

That was a week before Hurricane Katrina. The school: The University of New Orleans.

Once upon a time we believed in keeping off-site backups. Katrina taught us how short-sighted this is. Now we know that off-site backups must be 1000 miles away. Mother Nature has been angry of late, and it turns out she can take out a city.

So can the bad guys. Or, they will be able to before too many years go by. Though it hurts to think about the possibility, wise companies, especially those located in a dense metropolis, are at risk from all sorts of attacks. Lose the building or the city and all of the data preserved there will be gone.

Then there's the threat of EMP. The Wikipedia entry (http://en.wikipedia.org/wiki/Electromagnetic_pulse) is practically a handbook for designing an EMP attack. Some correspondents claim, and I don't know if this is true, that solar events can cause EMP-like effects.

This all sounds greatly alarmist, but risk management is an essential part of running a team. The greatest asset most of our groups have is probably our IP, represented in CAD drawings and source code. A fire, water damage or a rogue employee can take our all of the locally-stored IP. Other factors, like the ones listed above, can destroy even off-site backups.

Keep a backup in another state.

A lot of folks use the cloud. There are a lot of services out there, like JungleDisk, which encrypt your code and feed it into networks of servers. Your legal group may have issues with this, but it's a technically-attractive solution. One wonders, however, what an EMP-like event would do to a server farm.

Someday the accountants will realize just how much of a company's value is tied up in source code. Till that day we engineers have to protect this vital, and all-too-vulnerable, asset.

Of course, according to this (http://www.physorg.com/news162061022.html) we may soon get non-volatile memory good for a billion years!