 when we are restoring a db using automated backup it is getting error while provisioning

Question

 when we are restoring a db using automated backup it is getting error while provisioning

Yadhu Krishnan 0

getting this error while restorong the db

{ "code": "DeploymentFailed", "target": "/subscriptions/fdcf8a78-634f-4b78-ac98-56c2e655226f/resourceGroups/CSL-Database/providers/Microsoft.Resources/deployments/RestoreMySQLFlexibleServer_ad9cfc9353bf446cafbe4c33e43b5d31", "message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.", "details": [ { "code": "ResourceDeploymentFailure", "target": "/subscriptions/fdcf8a78-634f-4b78-ac98-56c2e655226f/resourceGroups/CSL-Database/providers/Microsoft.DBforMySQL/flexibleServers/corestart-ind", "message": "The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'." } ] }

[
  {
    "id": "/subscriptions/fdcf8a78-634f-4b78-ac98-56c2e655226f/resourceGroups/CSL-Database/providers/Microsoft.Resources/deployments/RestoreMySQLFlexibleServer_ad9cfc9353bf446cafbe4c33e43b5d31/operations/4627D648D89176EF",
    "operationId": "4627D648D89176EF",
    "properties": {
      "provisioningOperation": "Create",
      "provisioningState": "Failed",
      "timestamp": "2025-10-22T13:58:06.517158Z",
      "duration": "PT4M5.4491121S",
      "trackingId": "c8695012-a98e-492b-be46-7df78836602f",
      "statusCode": "Conflict",
      "statusMessage": {
        "status": "Failed",
        "error": {
          "code": "InternalServerError",
          "message": "An unexpected error occured while processing the request. Tracking ID: '90957553-b05b-4f60-9d68-3c78444785a8'"
        }
      },
      "targetResource": {
        "id": "/subscriptions/fdcf8a78-634f-4b78-ac98-56c2e655226f/resourceGroups/CSL-Database/providers/Microsoft.DBforMySQL/flexibleServers/corestart-ind",
        "resourceType": "Microsoft.DBforMySQL/flexibleServers",
        "resourceName": "corestart-ind"
      }
    }
  }
]

VRISHABHANATH PATIL 1,295 Reputation points Microsoft External Staff Moderator

2025-10-22T15:50:58.0966667+00:00
Hi Yadhu Krishnan,

Welcome to Microsoft Q&A Platform. Thank you for reaching out & hope you are doing well.

From what you have described, it looks like Azure had trouble restoring your MySQL Flexible Server basically, the platform hit an issue while trying to bring up the new server from backup. This can happen for a few different reasons, usually either a capacity issue in the region, a temporary backend problem, or a small configuration conflict.

Here’s what I suggest checking:

1.See what failed in detail In the Azure Cloud Shell or CLI, run:

--az deployment group operation list \ --resource-group CSL-Database \ --name RestoreMySQLFlexibleServer_ad9cfc9353bf446cafbe4c33e43b5d31

This shows the specific step that failed and gives you a tracking ID. Please share that if you can.

2.Look at the Activity Log In the Azure portal, go to Monitor → Activity Log, filter by your resource group (CSL-Database), and check around the time it failed. Look for entries showing “Failed” or “Conflict.”

3.Check Azure Service Health Sometimes restores fail because of a temporary issue or lack of available capacity in that region. It’s worth checking the Service Health page to see if anything is going on in your region.

4.Try restoring again with a different setup If this keeps failing, try:

A different server name (to avoid naming conflicts).

A different SKU or region, just to rule out capacity limits.

A manual restore using Azure CLI instead of portal restore — that sometimes bypasses transient errors.

5.If it still fails Since your error includes tracking IDs like 90957553-b05b-4f60-9d68-3c78444785a8, it’s best to open a support case with Microsoft. Include:

The deployment name (RestoreMySQLFlexibleServer_ad9cfc9353bf446cafbe4c33e43b5d31)

The error message and tracking IDs

The time it failed (UTC time) This lets the backend team check the actual logs to see if it’s a capacity or platform issue.

Do let us know if you have any questions and queries.

Thanks,
Manoj
Yadhu Krishnan 0 Reputation points

2025-10-23T04:57:11+00:00

can you please help me on raising the ticket
VRISHABHANATH PATIL 1,295 Reputation points Microsoft External Staff Moderator

2025-10-23T08:13:19.16+00:00

Hi Yadhu Krishnan,

To continue the investigation, we’ve requested some details in the Private Message section. Kindly provide those details.

We request you to follow those steps and share your updates so we can proceed with further investigation.

Note: Please avoid creating multiple questions for the same issue, as we are actively working to address your query. In the initial comment section, we shared a few steps to help resolve your question.

I have closed the other similar threads as duplicates, and we will continue our discussion in this question. Please DO NOT respond on duplicate question created recently.

Thanks,
Vrishabh
VRISHABHANATH PATIL 1,295 Reputation points Microsoft External Staff Moderator

2025-10-23T10:08:17.14+00:00
Hi Yadhu Krishnan,

Along with the initial solution, here are some additional details that may help you address your question.

Restore is failing with a generic DeploymentFailed, and inside that you’re seeing a ResourceDeploymentFailure for Microsoft.DBforMySQL/flexibleServers plus statusCode: Conflict and InternalServerError. In practice, that means Azure tried to spin up the new restored Flexible Server (PITR always creates a new server) and couldn’t complete provisioning. The most common culprits are:

A name/DNS conflict or a networking mismatch (VNet/Private DNS/delegated subnet).

Regional capacity or subscription access limits in the target region.

A transient platform hiccup during server bootstrap.

Reference: Troubleshoot common Azure deployment errors https://free.blessedness.top/en-us/azure/azure-resource-manager/troubleshooting/common-deployment-errors

Quick checks (do these first)

Use a truly new server name and follow the official restore steps (PITR always restores to a new server).

Portal: https://free.blessedness.top/en-us/azure/mysql/flexible-server/how-to-restore-server-portal

CLI (syntax reference): https://docs.azure.cn/en-us/mysql/flexible-server/how-to-restore-server-cli

Open the failed deployment → Operation details to read the full inner error and capture the correlation/tracking ID. It often tells you whether it’s a conflict, quota, or network issue.

How to inspect deployment history/operations: https://free.blessedness.top/en-us/azure/azure-resource-manager/templates/deployment-history

Error catalog & mitigations: https://free.blessedness.top/en-us/azure/azure-resource-manager/troubleshooting/common-deployment-errors

Retry the restore. If it’s transient, a second attempt often succeeds. If it still fails, try a nearby AZ/region.

Likely causes & how to fix each

Name or DNS conflict (matches Conflict)

Make sure the new server name has never been used.

If you use Private Access (VNet integration), check for stale A records in your Private DNS zone and verify the delegated subnet is correct.

Networking overview (public, private endpoint, VNet): https://free.blessedness.top/en-us/azure/mysql/flexible-server/concepts-networking

VNet integration & delegated subnet requirements: https://free.blessedness.top/en-us/azure/mysql/flexible-server/concepts-networking-vnet

Delegated subnet out of IPs (private access)

Restores need IPs from the delegated subnet (HA = 2 IPs, non‑HA = 1). If the subnet is tiny (e.g., /29) or nearly full, provisioning fails.

Expand the subnet or pick a larger, properly delegated subnet and retry.

Subnet sizing/details: https://free.blessedness.top/en-us/azure/mysql/flexible-server/concepts-networking-vnet

Region capacity or subscription access

Sometimes the region limits who can deploy new MySQL Flexible Servers (or capacity is tight).

Ensure your subscription is registered with Microsoft.DBforMySQL and, if needed, submit a quota/region access request for the target region.

Error guidance: https://free.blessedness.top/en-us/azure/azure-resource-manager/troubleshooting/common-deployment-errors

Region access/quota process (Q&A walkthrough): https://free.blessedness.top/en-us/answers/questions/2280001/error-while-trying-to-deploy-azure-database-for-my

Capacity/region access article (source): https://github.com/MicrosoftDocs/azure-databases-docs/blob/main/articles/mysql/flexible-server/resolve-capacity-errors.md

CLI parameter issues (source-server)

If you’re scripting the restore, make sure --source-server is the Resource ID or server name, not a local file path.

Example and explanation: https://stackoverflow.com/questions/77759094/error-when-passing-the-source-server-to-restore-mysql-server

CLI reference (syntax mirror): https://docs.azure.cn/en-us/mysql/flexible-server/how-to-restore-server-cli

Transient platform error

Try the restore again (new name). If a new server gets stuck, use Self‑Heal (preview) in the portal to unstick common bootstrap issues.

Self‑Heal: https://free.blessedness.top/en-us/azure/mysql/flexible-server/how-to-self-heal

A short, practical playbook

Portal → Restore your source server → pick Latest or a Custom point in time → enter a new unique server name → create.

Portal steps: https://free.blessedness.top/en-us/azure/mysql/flexible-server/how-to-restore-server-portal

Using Private Access?

Confirm the delegated subnet is large enough and properly delegated; clean up any stale Private DNS records.

VNet/DNS specifics: https://free.blessedness.top/en-us/azure/mysql/flexible-server/concepts-networking-vnet

If it fails again

Check Operation details and note the correlation ID.

If capacity/region access is suspected, file a quota/region access request for MySQL Flexible Server in that region.

Deployment history & correlation ID: https://free.blessedness.top/en-us/azure/azure-resource-manager/templates/deployment-history

Quota/region access flow: https://free.blessedness.top/en-us/answers/questions/2280001/error-while-trying-to-deploy-azure-database-for-my

FYI: how backups/restores behave

Flexible Server keeps daily snapshots + 5‑minute log backups within your retention window (1–35 days, default 7). Restores always create a new server (you then point apps to it).

Concepts & rétention: https://free.blessedness.top/en-us/azure/mysql/flexible-server/concepts-backup-restore

Portal restore flows (Latest/Custom/Fastest): https://free.blessedness.top/en-us/azure/mysql/flexible-server/how-to-restore-server-portal

Thanks,
Vrishabh
Manoj Kumar Boyini 330 Reputation points Microsoft External Staff Moderator

2025-10-25T05:40:25.4766667+00:00

Hi Yadhu Krishnan,

I hope you had a chance to review the information shared earlier, and I hope this information has been helpful! If you still have questions, please let us know what is needed in the comments so the question can be answered.

Thanks,
Manoj

Your answer

Yadhu Krishnan 0 Reputation points

2025-10-23T04:57:11+00:00

can you please help me on raising the ticket
VRISHABHANATH PATIL 1,295 Reputation points Microsoft External Staff Moderator

2025-10-23T08:13:19.16+00:00

Hi Yadhu Krishnan,

To continue the investigation, we’ve requested some details in the Private Message section. Kindly provide those details.

We request you to follow those steps and share your updates so we can proceed with further investigation.

Note: Please avoid creating multiple questions for the same issue, as we are actively working to address your query. In the initial comment section, we shared a few steps to help resolve your question.

I have closed the other similar threads as duplicates, and we will continue our discussion in this question. Please DO NOT respond on duplicate question created recently.

Thanks,
Vrishabh
Manoj Kumar Boyini 330 Reputation points Microsoft External Staff Moderator

2025-10-25T05:40:25.4766667+00:00

Hi Yadhu Krishnan,

I hope you had a chance to review the information shared earlier, and I hope this information has been helpful! If you still have questions, please let us know what is needed in the comments so the question can be answered.

Thanks,
Manoj

Share via

 when we are restoring a db using automated backup it is getting error while provisioning

Your answer