Live data from Hacker News

Fire declared in OVH SBG2 datacentre building

travaux.ovh.net

481–490 of 613 posts

Re: Fire declared in OVH SBG2 datacentre building

#481

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…

Pictures from the fire: https://www.dna.fr/amp/faits-divers-justice/2021/03/10/stras...

This looks like yet another aluminium composite panel fire...

Re: Fire declared in OVH SBG2 datacentre building

#483
post #459

Earlier quoted context omitted.

I like scalingo too. If you need a bit more, they have DBaaS, APP Containers and Networking.

Scalingo is €552.96/m for 16GB of memory. 32c xeon/256GB ECC/500GB SSD 8TB HDD is $100/m at OVH. The difference is amusing.

you're comparing a PaaS with a piece of hardware. It's absolutely not comparable.

Yann, CEO at Scalingo

Re: Fire declared in OVH SBG2 datacentre building

#484

Earlier quoted context omitted.

Got burned once (no pun intended), learned my lesson. Hot spare on a different continent with replicated data along with a third box just for backups. The backup box gets offsite backups held in a safe with another redundant copy in another site in another safe. Restores are tested quarterly. Keep backups of backups. Once bitten, twice shy.

> Hot spare on a different continent Just be cautious about data locality laws (not likely to affect you as joe average, more for businesses)

A few years ago I worked on the British Telecom Worldwide intranet team and we had a matrix mapping various countries encryption laws.

This was so we remained legal in all of the countries BT worked in which required a lot of behind the scenes work to make sure we didn't serve "illegaly encypted" Data.

Re: Fire declared in OVH SBG2 datacentre building

#485

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…

I'm at OVH as well (in the BHS datacenter, fortunately). I run my entire production system on one beefy machine. The apps and database are replicated to a backup machine hosted with Hetzner (in their Germany datacenter). I also run a tiny VM at OVH which proxies all traffic to Hetzner. I use a failover IP to point at the big rig at OVH. If the main machine fails, I move the failover IP to the VM, which sends all traf…

are your domains at ovh too ? If yes, I'd consider changing this: this morning the manager was quite flooded and the DNS service was down for some time...

Re: Fire declared in OVH SBG2 datacentre building

#486

Earlier quoted context omitted.

is that entirely cargo containers? is that common for a data center?

https://en.wikipedia.org/wiki/Modular_data_center Container DCs were a big thing for a while. Even Google did a whole PR thing about how they used them.

Funnily enough, I think it was the fire risk that caused them to ditch the idea and move to their current design. Though I know modular design is highly likely to be used by all players as edge nodes spring up worldwide.

Re: Fire declared in OVH SBG2 datacentre building

#487
post #263

Earlier quoted context omitted.

Would you humor us with a link to a fully fire proof datacenter?

Newly constructed datacenters in the US tend to be all metal with a full building clean suppression agent. https://www.fike.com/products/ecaro-25-clean-agent-fire-supp... I used to work for a provider whose 2 main datacenters of 8k+ sq ft could pull all oxygen out of the building in 60 seconds.

Data centres I used to work in back in the early 2000s had argonite gas dumps in place (prior to argonite, halon used to be popular but is an ozone depleting gas so was phased out)

In the case of a fire, it would dump a lot of argonite gas in and consume a large amount of the oxygen in the room, depriving the fire of fuel. It's also safe and leaves minimal clean-up work afterwards, doesn't harm electronics etc. unlike sprinklers and the like.

The amount of oxygen left is sufficient for human life, but not for fires, though my understanding is that it can be quite unpleasant when it happens. You won't want to hang around.

Re: Fire declared in OVH SBG2 datacentre building

#489

Earlier quoted context omitted.

https://en.wikipedia.org/wiki/Modular_data_center Container DCs were a big thing for a while. Even Google did a whole PR thing about how they used them.

Funnily enough, I think it was the fire risk that caused them to ditch the idea and move to their current design. Though I know modular design is highly likely to be used by all players as edge nodes spring up worldwide.

It was also that the container had literally no advantages. It was just a meme that did not survive rational analysis. The building in which the datacenter is located is the simplest, cheapest part of the design. Dividing it up into a bunch of inconveniently-sized rectangles solves nothing.

Re: Fire declared in OVH SBG2 datacentre building

#490
post #121

Earlier quoted context omitted.

> Fire destroyed SBG2 This is crazy. SBG2 was HUGE and if this isn't a translation error on the part of Octave (which I could understand given the stress and ESL) I have a hard time fathoming what kind of fire could destroy a whole facility with nearly 1000 racks of equipment spread out across separated halls. I'm really hoping "destroyed" here means "we lost all power and network core and there's smoke/fire/physical…

No, "destroyed" looks like this: https://mobile.twitter.com/abonin_DNA/status/136953802824345... EDIT a picture from earlier this night https://pbs.twimg.com/media/EwGqV17XMAMF_wa?format=jpg&name=...

I'm really shocked, that's an incredible amount of damage. Lots of people lost data.
Post reply on HN