291–300 of 613 posts
Earlier quoted context omitted.
Easy to see now that a lightly constructed five story cube might not be a fully fire proof.
Would you humor us with a link to a fully fire proof datacenter?
Earlier quoted context omitted.
Or disaster prevention. I'm curious how their fire suppression system failed so spectacularly..
I think they failed to install it. They only mention smoke detection: https://www.ovh.com/world/us/about-us/datacenters.xml
The classic "lp0 on fire" error message comes to mind: https://en.wikipedia.org/wiki/Lp0_on_fire Really though, I feel truly awful for anyone affected by this. The post recommends implementing a disaster recovery plan. The truth is that most people don't have one. So, let's use this post to talk about Disaster Recovery Plans! Mine: I have 5 servers at OVH (not at SBG) and they all back up to Amazon S3 or Backblaze B2…
The classic "lp0 on fire" error message comes to mind: https://en.wikipedia.org/wiki/Lp0_on_fire Really though, I feel truly awful for anyone affected by this. The post recommends implementing a disaster recovery plan. The truth is that most people don't have one. So, let's use this post to talk about Disaster Recovery Plans! Mine: I have 5 servers at OVH (not at SBG) and they all back up to Amazon S3 or Backblaze B2…
They both run postfix + dovecot, so mail is synced via dovecot replication. Data is rsync-ed daily, and everything has ZFS snapshots. MySQL is not set into replication - my home internet breaks often enough to have serious issues, so instead I drop everything every day import a full dump from the main server, and do a local dump as backup on both sides.
I don't have automatic failover set up.
According to the official status page, the whole datacenter is still green http://status.ovh.com/vms/index_sbg2.html
You're completely right. IMO this is the best comment in this whole thread. Their status page must be broken, or it's a lie.
Earlier quoted context omitted.
OVH design their own datacenters, so it's possible that they missed something or some system or another didn't work as intended, thus the heavy damage.
They did not have a fire suppression system, only smoke detection. So yeah, they missed something.
Earlier quoted context omitted.
I'm not sure if it's because my tolerance of Graham Linehan has snapped or not, but I barely laugh at the IT Crowd any more. As with other GL shows I find it's just mostly held together but the cast's delivery and such The laugh track and the writing is honestly dated even by the standards of Dads Army.
I don't remember the details, but I think that season 2 kind of retroactively ruined season 1. They used to have all those O'Reilly and EFF stickers, and working at a help desk at the time, it felt very authentic. Then everything got super nice in season 2 -- leather couches, people were dressing nicely, etc. It kind of lost its charm. You can't rewatch it because you know Denholm is just going to randomly jump out o…
That sounds like a pretty realistic allegory of the last two decades in Free Software (or software in general, or the web...)
Most modern data centres wouldn't have had this issue, at least in in Australia they use Argonite suppression systems, these work by using a gas that is a mixture of argon and nitrogen that suppresses fire by depleting oxygen in the the data hall.
I'm seeing quite a lot of repeated sentiment throughout the comments that Halon is illegal and is no longer used. Is the situation "Halon is legal in Australia" or "Halon isn't actually illegal per se if you don't use a lot of it"?
The classic "lp0 on fire" error message comes to mind: https://en.wikipedia.org/wiki/Lp0_on_fire Really though, I feel truly awful for anyone affected by this. The post recommends implementing a disaster recovery plan. The truth is that most people don't have one. So, let's use this post to talk about Disaster Recovery Plans! Mine: I have 5 servers at OVH (not at SBG) and they all back up to Amazon S3 or Backblaze B2…
Turns out, our disaster recovery plan is pretty good.
Datacenter burned down and I still was up 4 hours later in another data center with zero data loss. Good times.