Earlier quoted context omitted.
Bacula has some really cool features for cloud backups. https://bacula.org
Ow what an unfortunate name. https://en.wikipedia.org/wiki/Baculum
but fortunately also within arm's reach
Fire declared in OVH SBG2 datacentre building
221–230 of 613 posts
Re: Fire declared in OVH SBG2 datacentre building
#222Earlier 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.
Which is understandable, as Halon based fire suppression systems have been illegal for quite some time :/
Re: Fire declared in OVH SBG2 datacentre building
#223To my experience, backups in companies are barely done.
Companies want quick money, they push people to skip important IT operations, like disaster recovery plans.
And backups are the least monitored systems.
Re: Fire declared in OVH SBG2 datacentre building
#224Re: Fire declared in OVH SBG2 datacentre building
#225Earlier quoted context omitted.
Duplicity is your best bet for incremental backups using B2. I use this for my personal server and it works brilliantly.
I thought so too for a long while. Until I was trying to restore something (just to test things), and wasn’t able to... it might have been specific to our GPG or an older version or something... but I decided to switch to restic and am much happier now. Restic has a single binary that takes care of everything. It feels more modern and seems to work really well. Never had any issue restoring from it. Just one data poi…
+1 for Restic
It's brilliant, works like a charm on freebsd windows and a rpi with linux since over 2 years.
Re: Fire declared in OVH SBG2 datacentre building
#226Here is some pics of what it looked like before, spg 1-4 , and it’s history https://baxtel.com/data-center/ovh-strasbourg-campus
I'm surprised to see how close the DCs are to the river.
Fortunately it's in the high part of the river, less prone to overflow.
Re: Fire declared in OVH SBG2 datacentre building
#227A status update on the OVH tracker for a different datacenter (LIM-1 / Limburg) says "We are going to intervene in the rack to replace a large number of power supply cables that could have an insulation defect." [0][1] The same type of issue is "planned" in BHS [3] and GRA [2]. Eerie timing: do they possibly suspect some bad cables? [0]: http://travaux.ovh.net/?do=details&id=49016 [1]: http://travaux.ovh.net/?do=deta…
https://www.google.com/search?q=site%3Ahttp%3A%2F%2Ftravaux.... there's quite a few of these
http://travaux.ovh.net/?do=details&id=47840 earliest one that I found was back in December
Re: Fire declared in OVH SBG2 datacentre building
#228The 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…
Personal: I run a webserver for some website (wordpress + xenforo), I've set up a cronjob that creates a backup of /var/www, /etc and a mysql database dump, then uploads it to an S3 bucket (with automatic Glacier archiving after X period set up). It should be fairly straightforward to rent a new server and set things back up. I still dislike having to set up a webserver + php manually though, I don't get why that has…
Have you considered writing an ansible playbook to set all that up? You could even have it pull down the backup and do a full restore for you...
Re: Fire declared in OVH SBG2 datacentre building
#229Re: Fire declared in OVH SBG2 datacentre building
#230I don’t know what ovh is and going to the site point me to a speed test with no information.
Imagine AWS, with less features, but 10x-100x lower prices. And now you know why until a few years ago they were larger in traffic, customers, and number of servers than even AWS.