OVHcloud Web Hosting Status

Current status
Legend
  • Operational
  • Degraded performance
  • Partial Outage
  • Major Outage
  • Under maintenance
SharedSQL sql002 & sql004
Scheduled Maintenance Report for Web Cloud
Completed
En avril 2019, nous avons introduit les premières bases de données managées sur du stockage ultra-rapide NVMe.

Nous avons d'abord créé toutes les nouvelles instances SharedSQL, PrivateSQL et CloudDB sur ce nouveau matériel. Puis, nous avons migré les CloudDB (réseau publique). On s'est ensuite occupé de migrer massivement les 800000 SharedSQL et 12000 PrivateSQL du centre de données de P19. Cette migration est désormais terminée, nous entamons maintenant le chantier de migration des derniers SharedSQL de Gravelines vers ce nouveau matériel.

Les migrations des SharedSQL de Gravelines, clusters sql002 et sql004, seront faites ces prochaines semaines. Elles entraîneront une coupure de 5 minutes environ par instance.

Notez que les migrations du cluster sql001 viennent de se terminer: http://travaux.ovh.net/?do=details&id=42082 ; sql002 et sql004 sont les 2 derniers clusters à passer sur des clusters NVMe.

---

In April 2019, we introduced the first managed databases based on ultra-fast NVMe storage.

We first created the new SharedSQL, PrivateSQL and CloudDB instances on this new hardware. Then, we migrated the CloudDB (public network). We then moved massively the 800000 SharedSQL and 12000 PrivateSQL of the P19 datacentre. This migration is now over. We now begin the migration of the last Gravelines' SharedSQL to this new hardware.

The migration of the SharedSQL of Gravelines, sql002 and sql004 clusters, will be done on the next weeks. A 5 minutes downtime is expected per instance.

Note that the sql001 migrations just ended: http://travaux.ovh.net/?do=details&id=42082 ; sql002 and sql004 are the 2 last clusters to move on NVMe clusters.

Update(s):

Date: 2020-05-14 14:30:59 UTC
Here we are! The migrations are now over.

Enjoy =)

Date: 2020-05-14 07:16:11 UTC
Intervention completed successfully at 1:00 CEST

Date: 2020-05-13 21:50:51 UTC
The intervention is starting…

That's the last one! =D

Date: 2020-05-13 06:48:32 UTC
Intervention completed successfully at 2:00 CEST

Date: 2020-05-12 06:49:22 UTC
Intervention completed successfully at 3:00 CEST

Date: 2020-05-11 21:59:57 UTC
The intervention is starting…

Date: 2020-05-08 15:35:13 UTC
Next and last interventions:
- db00[4-7].sql002 and db00[4-7].sql004, on 2020-05-11, from 23:00 CEST.
- db00[1-3].sql002, db003.sql004 and db002.sql004 (part 1/2), on 2020-05-12, from 23:00 CEST.
- db002.sql004 (part 2/2) and db001.sql004, on 2020-05-13, from 23:00 CEST.

Date: 2020-05-07 19:43:35 UTC
As tomorrow is a public holiday in France, we'll postpone today's intervention to Monday, 2020-05-11.

Date: 2020-05-05 15:13:48 UTC
Next intervention:
- db00[4-7].sql002 and db00[4-7].sql004, on 2020-05-07, from 23:00 CEST.

Date: 2020-05-05 07:02:19 UTC
Interventions completed successfully at 3:00 CEST

Date: 2020-05-04 21:35:03 UTC
The intervention is starting…

Date: 2020-04-29 19:30:04 UTC
Next intervention:
- db0[08-13].sql002 and db0[08-11].sql004, on 2020-05-04, from 23:00 CEST.

Date: 2020-04-29 07:33:47 UTC
Intervention completed successfully at 3:00 CEST

Date: 2020-04-28 21:45:32 UTC
The intervention is starting…

Date: 2020-04-24 21:15:24 UTC
Next interventions:
- db01[7-9].sql002 and db01[4-5].sql004, on 2020-04-27, from 23:00 CET.
- db01[4-6].sql002 and db01[2-3].sql004, on 2020-04-28, from 23:00 CET.

Date: 2020-04-24 07:13:59 UTC
Interventions completed successfully at 1:45 CEST

Date: 2020-04-23 21:36:58 UTC
The intervention is starting…

Date: 2020-04-23 07:05:45 UTC
Intervention finished at 03:00 for db02[2-5].sql002 and db01[8-9].sql004

Date: 2020-04-22 22:28:24 UTC
The intervention is starting…

Date: 2020-04-22 13:45:46 UTC
Next interventions:
- db02[2-5].sql002 and db01[8-9].sql004, on 2020-04-22, from 23:00 CET.
- db02[0-1].sql002 and db01[6-7].sql004, on 2020-04-23, from 23:00 CET.

Date: 2020-04-22 06:58:39 UTC
Intervention finished at 2:00 CET for db02[6-7].sql002 and db02[0-1].sql004

Date: 2020-04-21 21:31:49 UTC
The intervention is starting…

Date: 2020-04-21 06:16:17 UTC
Intervention completed successfully at 3:00 CET for db02[8-9].sql002

Intervention completed successfully at 3:40 CET for db02[2-3].sql004

Date: 2020-04-20 22:46:26 UTC
The intervention is starting…

Date: 2020-04-17 18:32:21 UTC
Next interventions:
- db02[8-9].sql002 and db02[2-3].sql004, on 2020-04-20, from 23:00 CET.
- db02[6-7].sql002 and db02[0-1].sql004, on 2020-04-21, from 23:00 CET.

Date: 2020-04-16 22:02:16 UTC
Intervention completed at 21:59 CET.

Date: 2020-04-16 21:15:58 UTC
The intervention is starting…

Date: 2020-04-16 12:15:43 UTC
Next intervention:
- db024.sql004, on 2020-04-16, from 23:00 CET.

Date: 2020-04-16 07:18:15 UTC
Intervention completed successfully at 3:00 CET for db03[0-1].sql002 and db025.sql004.
Intervention postponed for db024.sql004.
All databases are up and running

Date: 2020-04-15 21:45:12 UTC
The intervention is starting…

Date: 2020-04-15 07:00:11 UTC
Intervention completed successfully at 3:00 CET for db03[2-3].sql002

Intervention completed successfully at 2:45 CET for db02[26-7].sql004

Date: 2020-04-14 22:00:29 UTC
The intervention is starting…

Date: 2020-04-09 14:09:28 UTC
Next interventions:
- db03[2-3].sql002 and db02[6-7].sql004, on 2020-04-14, from 23:00 CET.
- db03[0-1].sql002 and db02[4-5].sql004, on 2020-04-15, from 23:00 CET.

Date: 2020-04-09 07:51:55 UTC
Intervention completed successfully at 6:50 CET for db03[4-6].sql002

Intervention completed successfully at 8:30 CET for db0[28-30].sql004

Date: 2020-04-08 22:28:40 UTC
The intervention is starting…

Date: 2020-04-08 07:12:43 UTC
Intervention completed successfully at 4:30 CET for db03[7-8].sql002

Intervention completed successfully at 2:30 CET for db031.sql004

Intervention on db030.sql004 was delayed

Date: 2020-04-07 21:43:56 UTC
The intervention is starting…

Date: 2020-04-07 07:17:21 UTC
Intervention completed successfully at 1:50 CET

Date: 2020-04-06 21:36:33 UTC
The intervention is starting…

Date: 2020-04-01 18:38:53 UTC
Next interventions:
- db039.sql002, on 2020-04-06, from 23:00 CET.
- db03[7-8].sql002 and db03[0-1].sql004, on 2020-04-07, from 23:00 CET.
- db03[4-6].sql002 and db02[8-9].sql004, on 2020-04-08, from 23:00 CET.

Date: 2020-03-26 22:35:43 UTC
Intervention on db03[2-5].sql004 finished at 20:50 UTC.
That was quite long, but everything went good.

Date: 2020-03-26 09:25:24 UTC
Missing databases on sql002 are now fixed

Intervention still in progress on sql004

Date: 2020-03-26 08:43:23 UTC
Intervention on db04[0-3].sql002 finished at 6:35 CET

All went well except for 7 databases, we are on it

Date: 2020-03-25 21:54:35 UTC
The intervention is starting…

Date: 2020-03-24 22:07:41 UTC
The intervention is postponed to tomorrow. Same hosts, same hours.

Date: 2020-03-23 21:51:21 UTC
Next intervention: db04[0-3].sql002 and db03[2-5].sql004, on 2020-03-24, from 23:00 CET.
Posted Mar 23, 2020 - 21:44 UTC
This scheduled maintenance affected: Web Hosting || Datacenter GRA (Cluster002, Cluster003, Cluster006, Cluster007, Cluster011, Cluster012, Cluster013, Cluster014, Cluster015, Cluster017, Cluster020, Cluster021, Cluster023, Cluster024, Cluster025, Cluster026, Cluster027, Cluster028, Cluster029, Cluster030, Cluster031).