MyTimetable database migration - user preferences

Additional system checks have been completed. The system is now in the state it was on Saturday morning. Of course, timetabling data is up to date.

We offer our sincerest apologies for the issues caused. Either today or tomorrow, we will reach out to each affected customer with:

1. A incident analysis on what has happened over the weekend, and how we prevent it from happening again
2. A detailed plan on how we will move forward with this migration and when

All affected customer environments have been rolled back one by one. We are now performing additional system checks to assure the rollback is successful.

We are receiving reports from customers about missing data. We will perform a rollback imminently for all customers that have been migrated over the weekend. This will take around 30 seconds downtime for each customer.

The maintenance is now complete and all systems are performing as expected. Thanks for your patience.

Data migrations have completed and we are performing system checks.

The scheduled maintenance is now underway. We'll keep you updated on our progress.

We will be performing maintenance work on the MyTimetable hosting platform on Saturday the 11th of November.

What will be done?

During this maintenance window we will migrate the following MyTimetable databases from our legacy to our new database infrastructure:

• MyTimetable 'user preferences' database

When will MyTimetable be unavailable?

Your MyTimetable might be unavailable for around 30-60 minutes at Saturday the 11th of November. The unavailability is required to make sure that no changes are made to the database during the migration.

Please note that many customers are already on the new database infrastructure, and will therefore not experience any interruption of the service at all.

Why is this necessary?

At the moment, MyTimetable is using two database infrastructures. We have decided to consolidate these into one infrastructure.

This improves the availability and resilience of our platform and allows us to offer point-in-time recovery for the abovementioned databases. Furthermore, the MyTimetable software only needs to support one infrastructure, allowing us to simplify the software and decrease the risk of database specific bugs.

Are there any risks involved?

The risk involved is considered low. Many customers are already using our new database infrastructure for years and we have included several checks in the migration process to make sure all data is copied over. When migrating the acceptance environments, no issues have occurred.

What will happen if the database migration fails?

If the migration fails or if MyTimetable is not working as expected, the change will be rolled back.