11–20 of 142 posts
Sounds like this wasn't caused by power surges reaching the equipment but rather an effect of repeated power loss to drive arrays not fully designed to handle it. The article is pretty unclear. Still sounds like an infrastructure problem though.
Earlier quoted context omitted.
The article mentions Compute Engine, which is an external offering that isn't really used internally. It's hard to say what else might have been affected, if anything, but going by the article this shouldn't be causing your problem.
Fair enough. One can hope.
Sounds like this wasn't caused by power surges reaching the equipment but rather an effect of repeated power loss to drive arrays not fully designed to handle it. The article is pretty unclear. Still sounds like an infrastructure problem though.
The incident report ismavis posted below (and linked in the article) has far more information: https://status.cloud.google.com/incident/compute/15056#57195...
Beyond security, this highlights one of the main issues with the cloud. Was there no backup? Of course once you get beyond the headline, I think most people are much worse with protecting themselves from rare outages than Google.
Unless I am specifically paying for backup service, I wouldn't expect/want them to do that for me. And even if I was, I'd still have offsite backups if the system was important.
If you aren't being responsible with your backups in a noisy environment like Google Cloud/AWS, understand that you are vulnerable to freak accidents like this. Google/AWS's job in all of this is to try to reduce the frequency of issues and to minimize the impact.
Curious - how do they know lightning hit four times? Was someone outside counting?
Assuming 1 petabyte of total storage at the datacenter, that equates to about 100mb. I wonder how much storage they have there.
> Google said that just 0.000001% of disk space was permanently affected. Assuming 1 petabyte of total storage at the datacenter, that equates to about 100mb. I wonder how much storage they have there.