k4be

@Flaabius @Krzyszt74572717 @olesovhcom "Customer rescue system" likely means you're lucky. Check your email for password to log in to the rescue system, then check the server and reboot it from hard disk. If no email, maybe just attempt rebooting from hard disk right away.

@k4be5 @Krzyszt74572717 @olesovhcom For me it's a little different, I have this rescue mode : "rescue64-pro (Customer rescue system (Linux))". Is the same as Krzyszt ? @olesovhcom si tu passes par là :)

We have a major incident on SBG2. The fire declared in the building. Firefighters were immediately on the scene but could not control the fire in SBG2. The whole site has been isolated which impacts all services in SGB1-4. We recommend to activate your Disaster Recovery Plan.

@Flaabius @Krzyszt74572717 @olesovhcom "Internal rescue" means they encountered some problems with that server and are working on it. Unfortunately, I've seen people saying their server stays in this state for days.

@Krzyszt74572717 @olesovhcom Same question for me.

@HubuFM @olesovhcom Why is there no S350 row on the monitoring page?

@leviBKL @olesovhcom "Internal rescue" means they are already working on it.

@olesovhcom @olesovhcom are you referring to all of them, our server is already connected to the network and in internal rescue mode. Please can you check it! Thank you!

@hycszy9j @olesovhcom There are no VPS on SBG1 and SBG4. Only dedicated.

@olesovhcom give vps clients to start it's vps on sbg4 instead sbg2

@SaadiSahbi @olesovhcom Mine keeps working for now.

@olesovhcom SBG4 down again? Why?

@Matteo997 @olesovhcom SBG2 was lost but your vps may have a backup stored somewhere that they can now restore.

@olesovhcom I am even more confused. I got a mail saying that my SBG2 vps will be restored. How is this possible? Wasn't it all lost forever? It's been a while since i restarted all in GRA, does this mean i won't get any refund appliable to the new one and that i will have to move again?

@ovh_support_fr Thank you for answering. I can't login to that service with my SYS account though :(

@k4be5 Hello, if you want to cancel your server, you can contact directly our billing team : ovh.com/manager/dedica… ^AlexL

@olesovhcom I've ordered a replacement server a week ago, hoping to get my non-commercial services back online quicker. Now the old SBG4 server is up, and the replacement one is still not. Should I cancel the replacement order to free up the new server for others? How do I do that?

Update March,27 9am SBG1/AD to SBG4 will be done by Tue SBG1/E to Croix Cleaning up will be de by Tue. All servers will be in the DC by Tue/Wed. Then it will be powered up & restart the network. Servers will be UP by Tue - Fri.

@olesovhcom My service at SBG4 is now online. Is it likely to be needed in the future, or should I cancel the replacement order to free the future server for someone needing it more? How do I request the cancelling?

Update March,26 7am 6/6 The servers SBG1 61E/62E are in the cleaning up process. The speed is 3 racks per day. We have 32 racks. We are looking how to speed up it. Some racks have already been shipped back to DC. Last step of the process is detecting remains «chlorure».

@olesovhcom My service at SBG4 is now online. Should I cancel the replacement order (as it is not yet delivered for now), or will it be useful soon?

Update March,24 6:30pm The cleaning takes time. We have 80 people (SBG3) + 20 people (Croix). On the left, a motherboard with the smoke pollution on the CPU socket. It’s very corrosive ! If we power up, it’s dead. Same the disk. On the right, the same device 24h after cleaned up

@olesovhcom "Travaux" says: "- Server restart : ETA: Wednesday, 25 March." I've checked, the closest future Wednesday at 25 March is in 2026. We'll just have to wait, we've already waited so that's not a problem.

Update March,23 2pm 3/3 vRack in SBG3: pCC: Today we are rebuilding the gateway vRack. then the team will resetup the vRack in the Area & between the Areas/DCs. Baremetal we are rebuilding 1 of 4 gateway from BM today. The last part of the vRack will be UP. pCI All UP.

@HalloLaTerre @olesovhcom twitter.com/olesovhcom/sta…

Update 22 mars 6pm Une 3eme video avec le résumé de la situation, suite à l'incendie dans le DC SBG2. (english version asap)

@SawomirK3 @olesovhcom "We need 3 days to dig & connect power from SBG4 to SBG3." That may mean they'll start their work in Wednesday, as well as we'll see the servers up tomorrow evening. That's unpredictable.

@MakWxf @olesovhcom Current incident frequency is one every 9 days.

@olesovhcom My VPS is finally back online, it was long but at least I have the latest version of my data. Thanks BTW, do we have to fear some down time in the next hours/days or everything gonna stay online? I mean until the next incident...

@almuriuki @SawomirK3 @olesovhcom Read this. They already knew it all back in 2017. travaux.ovh.net/?do=details&id…

@k4be5 @SawomirK3 @olesovhcom No they screwed up big time by creating a point of failure. They should have run independent power lines to it, now they're repeating the same mistake with SBG3

@Ded3l @olesovhcom Backups are safe in their place. But it's no use when there's nowhere to extract the data. So i'm still waiting for the GRA service, should it be quicker. Also we already know from the 2017 incident, what happens if "separate" DCs are dependent on each other.

@k4be5 @olesovhcom SBG4 was up for hours. You should have make backups. Also at first, they didn't had to connect SBG4 to SBG3 since SBG1 was working great.

@Ded3l @olesovhcom They already had 11 days for this. I planned to set up the replacement service in GRA yesterday, as i have the data safely stored. Now that it's still not working, i will not have free time this week. I do not run a commercial service to engage all means to get another solution.

@k4be5 @olesovhcom Well go there and dig a hole for a 20kVA power cable. Then connect it.

@olesovhcom 3 days is not acceptable. If only the "free replacement" service was working...

Update March,21 9:30am SBG3: 40% of VPS are UP. Working hard 24/24 to restart the remain’s VPS. Working on pCS where we store the SBG2 backup service for VPS. SBG4: We need 3 days to dig & connect power from SBG4 to SBG3. SBG1: Building / moving a new A network room in SBG5.