I understand that it is "recommended" that App Services and Databases are backed up separately.
Can anyone confirm if the Azure App Service Backup is definitively NOT COMPATIBLE with MySQL 8?
It does not appear to be as I get an error relating to SSIS when I try to include a MySQL 8 connection in my App Service backup. However, it would be helpful for me to have a definitive and documented answer to this somewhere. I cannot find any official documentation on it.
Thanks,
Tim
Tim, Apologies for the delay in responding here.
While I’m checking on this internally with our product team and will also relay the feedback to our content author if this info needs to be clarified more explicitly.
What is the exact error message you receive?
At runtime, connection strings are available as environment variables, prefixed with the following connection types (examples)
• MySQL: MYSQLCONNSTR_ /or Custom: CUSTOMCONNSTR_
App Service can back up the database connected to your app (including App configuration and file content) to an Azure storage account and container that you have configured your app to use.
As documented here, the following database solutions are supported with backup feature SQL Database, Azure Database for MySQL, Azure Database for PostgreSQL and MySQL in-app.
However, the backups can be up to 10 GB of app and database content, up to 4GB of which can be the database backup. Typically, if the backup size exceeds this limit, you may get an error. As a side note, in case of the in-app MySQL databases, it’s automatically backed up without any configuration.
There are other requirement and restrictions, please see this doc section.
https://docs.microsoft.com/azure/app-service/manage-backup#requirements-and-restrictions
Hi. I have followed the procedures as documented and this has all worked for a long time until we switched to the latest azure mysql service. This is why I suspect the app backup system is not compatible with the new Azure Mysql 8 service. Have you been able to confirm this?
Thanks for the follow-up. I notice the same behavior on my tests. We have a generic note on this, in this doc - The MySQL 8.0.27 client is incompatible with Azure Database for MySQL - Single Server. All connections from the MySQL 8.0.27 client created either via mysql.exe or workbench will fail. As a workaround, consider using an earlier version of the client (prior to MySQL 8.0.27) or creating an instance of Azure Database for MySQL - Flexible Server instead.
I'm also discussing with the team to see if additional clarity on this is required in Azure App Service docs.
2 people are following this question.
