Need MS support, Our MySQL Flexible server migrated to Availability Zone 3 last night and as a result dirty shutdown logs exist which is concerning for data integrity

Question

Our MySQL Flexible server migrated From AZ1 to AZ3 last night at 23:05 (GMT+2) and as a result dirty shutdown logs exist which is concerning for data integrity, no Service health alerts, no platform health alerts as yet.

Can a support representative please contact me.

Answer 1

Hello Delmain !

Thank you for posting on Microsoft Learn Q&A.

from I’m not Microsoft support but I can help you identify the issue and if your problem still persist you need to open a support ticket.

In the Azure portal, open your MySQL Flexible Server and under resource health and check the timeline around that time because unplanned failovers are logged there as unavailable or unplanned events and grab the event time and ID.

https://learn.microsoft.com/en-us/azure/service-health/resource-health-overview

Then download the server error logs https://learn.microsoft.com/en-us/azure/mysql/flexible-server/how-to-server-logs-portal

You can also use CLI :

az mysql flexible-server server-logs download \
  -g <rg> -s <server-name> -n <log1> <log2> ...

What you’ll likely see is a normal InnoDB message like database was not shut down normally starting crash recovery and don't worry InnoDB is crash safe and runs page recovery automatically and check integrity if InnoDB recovery was completed cleanly:

SHOW ENGINE INNODB STATUS\G

You can open a support ticket https://learn.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request