Cannot turn on Geo-redundancy for Azure Database for MySql flexible server

Fabricio Rodriguez 26 Reputation points
2025-02-20T08:38:42.6633333+00:00

I have an Azure Database for MySql Flexible server instance in South Africa North. I created it with High Availability enabled. It's become too expensive, so I've had to turn HA off.

I would , however, like to turn on Geo-redundancy. When I tick the checkbox in Azure portal, the "Backup Redundancy Options" changes from "Zone-redundant" to "Geo-zone-redundant". I then click "Save". Azure starts deploying. After about a minute, it says:

"Deployment Failed
Deployment to resource group 'propworx-san' failed. Additional details from the underlying API that might be helpful: At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details."

When I click on "Deployment failed", it takes me to the Deployment page, where I see there is a Conflict error. Clicking on the error reveals this summary:

{
  "code": "InternalServerError",
  "message": "An unexpected error occured while processing the request. Tracking ID: 'fbeae12f-804d-442c-a232-88509a188006'"
}

Any ideas how I can proceed from here? Not sure how to get more detailed error messages so that I can try figure out what's going. on.

Thanks

Azure Database for MySQL
Azure Database for MySQL
An Azure managed MySQL database service for app development and deployment.
909 questions
{count} votes

Accepted answer
  1. Mahesh Kurva 2,830 Reputation points Microsoft Vendor
    2025-02-20T10:38:30.7933333+00:00

    Hi Fabricio Rodriguez,

    Welcome to Microsoft Q&A forum.

    As I understand, you're encountering an issue with the deployment of geo-redundancy for your Azure Database for MySQL Flexible Server instance.

    User's image Moving from zone-redundant to geo-redundant backup storage - Azure Database for MySQL Flexible Server doesn't support zone-redundant storage to geo-redundant storage conversion through Compute + Storage settings change after the server is provisioned. In order to move your backup storage from zone-redundant storage to geo-redundant storage, there are two options: a) Use PITR (point-in-time restore) to restore the server with desired configuration. b) Create a new server with the desired configuration and migrate the data using dump and restore.

    For more information, please refer the document: https://learn.microsoft.com/en-us/azure/mysql/flexible-server/concepts-backup-restore#backup-redundancy-options

    Hope this helps. Do let us know if you any further queries.

    If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.