Share via

How to restore Azure Database for MySQL flexible serve?

Aykut Sadi 0 Reputation points
2026-03-09T08:26:14.16+00:00

I am trying to restore the database from a specific point in time, but the restore process is failing repeatedly. We urgently require the database to be restored as soon as possible. Please assist in resolving this issue at the earliest.

Azure Database for MySQL

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. SAI JAGADEESH KUDIPUDI 1,825 Reputation points Microsoft External Staff Moderator
    2026-03-18T10:14:45.8833333+00:00

    Hi **Aykut Sadi,

    **The restore operation for Azure Database for MySQL Flexible Server was failing due to capacity constraints in the selected region while using the chosen SKU. The region did not have sufficient capacity to support the restore request with the Burstable SKU, which caused the restore operation to fail.

    The issue was resolved by modifying the restore configuration. The restore was retried by selecting an appropriate SKU, specifically changing from Burstable to General Purpose, and by ensuring the selected region had available capacity. After adjusting the SKU and retrying the restore operation, the restore completed successfully and a new server was created as expected.

    To avoid similar issues in the future, it is recommended to use the General Purpose SKU for restore operations, verify region capacity availability before initiating a restore, and enable geo‑redundant backups to provide more flexibility during restore scenarios.
    Reference Link:
    Backup and restore in Azure Database for MySQL – Flexible Server

    Hope this helps. If you have any follow-up questions, please let me know. I would be happy to help.

    Please do not forget to "up-vote" wherever the information provided helps you, as this can be beneficial to other community members.

    1 person found this answer helpful.
  2. Q&A Assist
    2026-03-09T08:26:42.03+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    Use a supported restore method and, because the restore is failing repeatedly and the database is urgently needed, follow a structured approach and then open a support case if it still fails.

    1. Validate basic restore conditions
    • Confirm that the server is Azure Database for MySQL – Flexible Server (not Single Server).
    • Ensure the point-in-time you are choosing is within the configured backup retention period.
    • If using Fastest Restore Point, select a full backup timestamp that is greater than the earliest restore point for that day; otherwise the restore can fail.
    1. Restore via Azure portal – point-in-time restore
    2. In the Azure portal, open the source Azure Database for MySQL – Flexible Server.
    3. Select Overview > Restore.
    4. Choose one of:
      • Latest restore point to restore to the most recent available time.
      • Custom restore point to specify an exact time.
      • Fastest Restore Point (Restore using full backup) to restore from a full backup only (fastest, but only to the backup completion time).
    5. For Fastest Restore Point:
      • Select Select fastest restore point (Restore using full backup).
      • Pick the desired full backup from Fastest Restore Point (UTC).
    6. Enter a new server name in Restore to new server.
    7. Select Review + Create, then Create.
    8. Wait for the notification that the restore operation has completed.
    9. Restore from a specific full backup (portal – Backup and Restore) If the point-in-time restore keeps failing, try restoring directly from a full backup:
    10. In the Azure portal, open the source MySQL Flexible Server.
    11. Select Backup and Restore.
    12. On Available Backups, locate the required full automated or on-demand backup within the retention period.
    13. Select Restore on the chosen backup.
    14. On the Restore page, the Fastest Restore Point option is preselected with that backup.
    15. Enter a new server name.
    16. Select Review + Create, then Create.
    17. Restore using Azure CLI (point-in-time) If portal restores fail, attempt a CLI restore to see detailed error output:
    18. Ensure Azure CLI is installed and logged in: 
          az login
    az account set --subscription <subscription id>
    19. Run a restore to a new server name and the desired UTC time: 
          az mysql flexible-server restore \
      --name <new-restored-server-name> \
      --resource-group <resource-group-name> \
      --restore-time "YYYY-MM-DDThh:mm:ssZ" \
      --source-server <source-server-name>
    20. Monitor the command output for any explicit error messages (for example, invalid time, outside retention, or missing backups).
    21. If moving from Public to Private access during restore If the restore is failing while changing networking (for example, to Private access):
    22. Start from Overview > Restore.
    23. Choose Geo restore or Point-in-time restore.
    24. Enter a new server name.
    25. Go to the Networking tab:
      • Set Connectivity method to Private access (VNet Integration).
      • Select a virtual network and subnet delegated to Microsoft.DBforMySQL/flexibleServers in the same region and subscription.
      • Create or select a Private DNS Zone ending with mysql.database.azure.com.
    26. Complete Review + create and then Create.
    27. If restores continue to fail and the database is urgent
    • Because the scenario is urgent and repeated restores are failing, open an Azure support ticket so backend engineers can inspect the backup chain and restore jobs.
    • Provide:
      • Source server name and region.
      • Exact restore time requested.
      • Whether using portal, CLI, or Backup vault.
      • Any error messages from the portal notifications or CLI output.
    1. Alternative: restore via Azure Backup vault (if configured) If the server is protected by Azure Backup (preview) for MySQL Flexible Server:
    2. Go to the Backup vault > Backup instances.
    3. Select Azure Database for MySQL – Flexible Server (preview) > Restore.
    4. Choose Select restore point and pick the required point in time (adjust Time period if needed).
    5. On Restore parameters, select Target Storage account and Target Container, then Validate.
    6. When validation succeeds, select Restore to recover the backups into the target storage account (from there, import into a new server if needed).

    Following these steps isolates whether the failure is due to the chosen time, backup availability, networking configuration, or a platform-side issue that requires Azure Support intervention.

    References:

    1 person found this answer helpful.
    0 comments

Your answer

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