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.
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)