It's easy enough to find an off-season vacation destination and move everyone there; essentially anywhere is cheaper than SF, so that's easy. Not every company has to move to the same place.
It'd suck to be a service-industry worker in SFBA after an earthquake, but tech employers can just move, and hire service-industry people to fix up their offices for a few months before returning (or not).
(this might not be necessary after a 7, but after something insane like a 9, would definitely happen)
Depending on the situation, earthquakes can bring fires and tsunamis. So what do you tell the network engineer that had their house burn to the ground? "Sorry for your lose; we're decamping for Las Vegas. Wheels up in 8 hours"?
If the big one does hit there is a lot more at stake than just your precious data.
1. Immediately call extra hands in other locations (datacenters, customer service, etc); begin over-time scheduling to alleviate need for workers in disaster zone. Doesn't require any coordination of disaster zone, just remaining executives located outside.
2. Offer two special payments to workers in the impacted zone: 1. Disaster recovery assistance, to help them cushion emergency needs and get their family/belongings/etc recovered faster; 2. Relocation bonus, to create an incentive for quick relocation to temporary (or new) office.
3. Spend as much as you to have to get extra emergency services in to the area, and generally assist in government/regional recovery area. This will free up the last of your staff for temporary relocation.
I doubt that a large company (we're talking Google, Microsoft, Facebook, etc) would take more than a couple days to have other sites working overtime to cover the load, less than a week to have already transported some of their staff to a new site, and less than a month to have brought almost all of the office back online.
This timeline, of course, assumes that the problem wasn't that their office fell on all their employees, killing them or something of that nature.
Likely, we'd see a hiccup in the development cycle, but in terms of keeping infrastructure online, emergency bug fixes, etc, we'd probably see relatively little damage.
1. In most businesses these other locations are supplementary to HQ. Typically there is no one at the datacenter and CS centers rely on guidance from HQ. They are not in the position to make decisions and drive the company.
2. Growing up and working in Florida you natural disasters are like clockwork. I can say for sure that 1 is covered by insurance and the gov't and 2 is going to be hard to pull off without looking like a complete dick. Also, you have other constraints. Airports may be closed and driving can be dangerous. Plus cars need fuel which is typically in short supply and expensive.
3. If you have a company of a few thousand I would say a few hundred are essential. Where are you going to find a place to house a few hundred people at once? Remember that other companies are thinking the same as well.
I also believe the most essential employees are that way for a reason. If they have the same preparedness in the company they also have the same mentality in their community. It would not be illogical to imagine the person in charge of DR for the company is also a member of the volunteer fire department.
Microsoft would be able to recover, then they find out the caterers don't have food to serve the cafeteria, employees can't come to work because there is no fuel, etc. These are the soft issues that most DR plans don't account for.
The end result was a high reliance on contract employees at the fail-overs, and a real appreciation for the human element.
But then again, I keep forgetting that the 'real' valley is just for early 20s-fresh-out-of-school-startup-single-guy-whizz-kids apparently.
If all your data is in your own building, you might be okay (assuming you can get at it, stuff it into a truck and move it out). Otherwise you're going to be waiting for a while.
There might be a run on laptops, monitors, chairs, etc which overwhelm the Hawaii and Las Vegas retailers for a while, but basically California's high energy costs, low power circuit availability, high sales/use tax on servers, etc have solved this problem already.
SFBA is critical for personnel, not so much manufacturing or hosting.
There is about 3mm square feet of datacenter space here. There are very few large companies which have servers only here and not somewhere outside the area but which would be reasonably expected to continue operating if their servers were somehow unaffected.
However, SFBA isn't even the first location for most companies I see. They go either into the cheaper AWS cloud regions (us east or the Oregon), or managed hosting somewhere (rarely SFBA).
Bay Area companies which directly get colo early on are fairly rare: stripe, square, etc. I fully support it as a strategy, but it is statistically insignificant.
Aside from price, east coast single location also gives you a lot better latency to Europe. Asia is usually screwed anyway, but the extra 80ms makes a big difference.
Well, putting everything in the Australian outback doesn't help that much, because there are good reasons why thousands of tech workers can't work there. This is essentially an argument against having any population centers in earthquake zones.
Which is an interesting point in and of itself.
http://www.nytimes.com/interactive/2011/05/01/weekinreview/0...
In the list of worst predictable natural disasters in the Continental US, it rates one above the expected earthquakes to the south, the result of two plates mostly sliding past each other: https://en.wikipedia.org/wiki/San_Andreas_fault
Worse, in part because we aren't at all prepared for it (aside from I hope more serious buildings) would be a return of major earthquakes in mid-West: https://en.wikipedia.org/wiki/New_Madrid_Seismic_Zone (something I pay attention to since that's on the other side of Missouri from me).
I forget one of them, and the worst, which few in the US would survive, and where being in Australia might not be a bad idea at all, would be a return of the Yellowstone Supervolcano: https://en.wikipedia.org/wiki/Yellowstone_Caldera
If the whole of the Americas was wiped off the Internet tomorrow then, for those of us in The Rest of The World (TM), life would go on. I think the only web property that would be annoying to not have would be Wikipedia. Second to that is the Google search engine but I take it as a given that they could cope just fine if America just mysteriously vanished one day.
I think that there are some that think that Silicon Valley is the centre of the universe, some indispensable magic place where all of the innovation happens. If there was The Big One (for the valley) we would soon find out exactly how important things like social networks and iphone apps really are. Life would go on. If anything, a big earthquake in Caliphonea is far preferable to a big eathquake in Japan. In Japan they make stuff the world needs.
If the whole of the Americas was wiped off the Internet
tomorrow then, for those of us in The Rest of The World
(TM), life would go on.
????What about the DNS roots, all the sites running on AWS, any site using Cloudflare or the JQuery/code.google.com CDN, etc
>DNS roots
http://www.iana.org/domains/root/servers
>AWS
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-reg...
>Cloudflare
https://www.cloudflare.com/network-map
>code.google.com CDN
https://developers.google.com/speed/libraries/devguide#Intro... - no location list though, only "globally available"
What we'll notice is not having filters for the pictures of our Starbucks cups. The demographic of teenage girls in malls will be devastated.
Silicon Valley is no longer the epicenter of technology; it's the epicenter of the fashion of technology.
It sounds like you're making an over-generalization based on the last few years of "social" while overlooking many of the largest tech companies in the world. Apple, Oracle, HP, Cisco, Google, Intel, the list goes on, are all headquartered here. http://www.siliconvalley.com/SV150/ci_25548370/
It was a poor place to make the comment; it wasn't on topic. My apologies. But when the comment was made that zillions of startups would be wiped out, and that we would notice, I wanted to clarify that we might notice but only in the most superficial way possible. Yes, it's a generalization -- there are always exceptions, and there are large tech companies there, but there are large companies in every major metropolitan area. If HP can't brand laptops for a year, I think we'll somehow manage to all survive.
I made the comment because I wanted to correct what I saw as an antiquated notion: that SV was different from Houston or Singapore. It used to be. It's not anymore.
If you want to look at devastating datacenter loss, if anything happened to Northern NJ the markets would go into a tailspin.
I'm just tired of the obviously incorrect proposition that Bay Area is producing just frivolous photo sharing and social communication tools (which both has a huge value for humanity, but that's a different story) and I seriously find it an interesting thought experiment what would happen on a global scale if the Bay Area would be devastated by a big earthquake.
The obvious tech giants like Google, Apple, Oracle and Cisco are arguably supporting a huge number of businesses and organizations around the world. But a glance through a list of just publicly traded US SaaS companies reveals that about 40% are from the Bay Area. These offer SaaS-based solutions ranging from HR tools (Workday), IT service monitoring (Splunk), ITMS (ServiceNow), CRMs (SalesForce), ERPs (NetSuite), Insurance backends (Guidewire) to supply chain management (e2open), to just name a few.
If Bay Area suffered anything resembling 2008 Sichuan earthquake, it would halt a good part of the economy for a while.
http://idlewords.com/bt14.htm#america
"And speaking of California, let me try another tack.
This festive map shows seismic hazard in Northern California, where pretty much all the large Internet companies are based, along with a zillion startups. The ones that aren't here have their headquarters in an even deadlier zone up in Cascadia.
Now of course, each company has four zillion datacenters, backed up across the world. But how much will that matter when there's a major quake, and Silicon Valley can't get to work for a month? All of these headquarters are going to be shut down for a long time when the Big One comes. You're going to notice it.
So even if you don't agree with my politics, maybe you'll agree with my geology. Let's not build a vast, distributed global network only to put everything in one place!"