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, cluster sql001, seront faites ces prochaines semaines. Elles entraîneront une coupure de 5 minutes environ par instance.
---
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, sql001 cluster, will be done on the next weeks. A 5 minutes downtime is expected per instance.
Update(s):
Date: 2020-03-20 08:36:32 UTC All done
Date: 2020-03-20 08:34:20 UTC Intervention completed successfully at 01h00 CET.
Date: 2020-03-19 21:59:14 UTC The intervention is starting…
Date: 2020-03-19 08:14:32 UTC Intervention completed successfully at 01h45 CET.
Date: 2020-03-18 22:25:12 UTC The intervention is starting…
Date: 2020-03-17 12:47:53 UTC Next interventions:
- db0[08-14].sql001 from 2020-03-18 23:15 CET.
- db00[2-7].sql001 from 2020-03-19 23:00 CET.
Date: 2020-03-03 13:25:32 UTC The last intervention will be on 2020-03-16, from 02:00 CET: db0[02-14].sql001.
Date: 2020-03-03 08:32:19 UTC The 4 databases have been fixed
Date: 2020-03-03 08:25:56 UTC Intervention completed successfully at 02h20 CET.
Except for 4 databases, which will be fixed soon
Date: 2020-03-02 22:26:53 UTC The intervention is starting…
Date: 2020-03-02 18:51:05 UTC Due to hardware on db001.sql001 (see http://travaux.ovh.net/?do=details&id=43228), the schedule changed a little bit.
Next intervention: db0[01,15-21].sql001 from 2020-03-02 22:30 CET.
Date: 2020-02-26 15:16:47 UTC Next intervention: db0[14-21].sql001 from 2020-03-02 22:30 CET.
Date: 2020-02-26 07:31:42 UTC Intervention completed successfully at 01h15 CET.
Date: 2020-02-25 22:01:49 UTC The intervention is starting…
Date: 2020-02-25 07:27:15 UTC Intervention completed successfully at 01h30 CET.
Date: 2020-02-24 21:39:01 UTC The intervention is starting on db0[29-34].sql001…
Date: 2020-02-11 18:51:41 UTC Next interventions:
- db0[29-34].sql001 from 2020-02-24 22:30 CET
- db02[3-4].sql001 and db02[6-8].sql001 from 2020-02-25 22:30 CET
Date: 2020-02-11 08:29:49 UTC Intervention completed successfully at 00h30 CET.
Date: 2020-02-10 21:34:39 UTC The intervention is starting…
Date: 2020-02-05 13:49:54 UTC Next intervention: db03[5-8].sql001 from 2020-02-10 22:00 CET.
Date: 2020-02-05 08:29:40 UTC Intervention completed successfully at 01:30 CET.
Date: 2020-02-04 22:07:43 UTC The intervention is starting…
Date: 2020-02-04 08:30:08 UTC Intervention completed successfully at 02:00 CET.
Date: 2020-02-03 22:03:44 UTC The intervention is starting…
Date: 2020-01-31 13:44:02 UTC Next interventions:
- db04[3-6].sql001 from 2020-02-03 22:30 CET
- db0[39-42].sql001 from 2020-02-04 22:30 CET
Date: 2020-01-31 08:31:34 UTC Intervention completed successfully at 02:00 CET.
Date: 2020-01-30 21:48:13 UTC The intervention is starting…
Date: 2020-01-24 13:43:59 UTC Next intervention: db04[7-8].sql001 from 2020-01-30 22:30 CET.
Date: 2020-01-24 08:18:24 UTC Intervention completed successfully at 03:10 CET.
Date: 2020-01-23 21:48:33 UTC The intervention is starting…
Date: 2020-01-16 20:35:37 UTC Next intervention: db0[49-50].sql001 from 2020-01-23 22:30 CET.
Date: 2020-01-16 08:25:40 UTC Intervention completed successfully at 03:35 CET.
Date: 2020-01-15 21:21:32 UTC The intervention is starting…
Date: 2020-01-15 16:57:21 UTC Next intervention: db05[1-2].sql001 from 2020-01-15 22:00 CET to about 2020-01-16 08:00 CET.
Date: 2020-01-15 09:00:55 UTC Intervention completed successfully at 09:14 CET.
Date: 2020-01-14 21:43:42 UTC The intervention is starting…
Date: 2020-01-14 13:45:38 UTC Next intervention: db05[3-5].sql001 from 2020-01-14 22:30 CET to about 2020-01-15 08:30 CET.
Date: 2020-01-14 08:14:58 UTC Intervention completed successfully at 05:29 CET.
Date: 2020-01-13 21:05:54 UTC The intervention is starting…
Date: 2020-01-10 15:48:03 UTC Next intervention: db05[6-7].sql001 from 2020-01-13 22:00 CET to about 2020-01-14 08:30 CET.
Date: 2020-01-10 08:52:01 UTC Intervention completed successfully at 06:24 CET.
Date: 2020-01-09 21:42:20 UTC The intervention is starting…
Date: 2020-01-08 23:13:20 UTC Intervention completed successfully.
Next one: tomorrow, from 22:30 CET. db05[8-9].sql001.
Date: 2020-01-08 20:57:43 UTC The intervention is starting on db060.sql001…
Date: 2020-01-07 21:52:57 UTC Intervention completed. Next migration tomorrow from 22:00 CET. db060.sql001, last part.
Date: 2020-01-07 21:32:18 UTC The intervention is starting on the second half of db060.sql001…
Date: 2020-01-03 19:21:16 UTC The next migrations will restart with db060.sql001 (part 2/2) on Monday, 2020-01-07 from 22:30 CET.
Date: 2019-12-19 00:06:58 UTC Intervention completed at 01:05 CET.
Date: 2019-12-18 21:29:38 UTC The intervention is starting on the first half of db060.sql001…
ETA: 01:50 CET.
Date: 2019-12-17 19:20:00 UTC Intervention completed at 19:51 CET.
Date: 2019-12-17 16:31:44 UTC The intervention is starting on db061.sql001.
Sorry for the intervention during the day for French people, but we're going to reach some limits if we don't do the intervention now.
Date: 2019-12-16 22:27:24 UTC Intervention completed. We will continue db061.sql001 tomorrow.
Date: 2019-12-16 22:10:46 UTC The intervention is starting on db061.sql001…
Posted Dec 16, 2019 - 22:05 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).