MyTimetable database migration (acceptance/test only)

The maintenance is now complete. Thanks for your patience.

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 next week. Please note this only applies to the acceptance and test environments.

Where we usually do not send out notices for this type of maintenance, we have chosen to do so this time as this maintenance will have some more impact on your acceptance and test environments than usual.

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
• MyTimetable External Calendar Integration database (for the Office 365 / Google Calendar integration)

Your timetabling databases will not be affected, as they are already on the new database infrastructure.

When will MyTimetable be unavailable?

Your MyTimetable test and acceptance instances will be unavailable for around 30 to 60 minutes at some point during the week. 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 downtime at all.

In case you are actively using your MyTimetable acceptance or test environment next week and want to either receive a more detailed date and time for this maintenance or want to postpone this maintenance, please contact us via Support.

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 will the production databases be migrated?

Production database migrations have not been scheduled yet. We will inform you at a later date of our plans, and will make sure to take into account peak times in teaching and will make sure the impact on end-users is as low as possible.