"{"code":"DeploymentFailed","target":"../deployments"At least one resource deploymen:Microsoft.SQLDatabase.newDatabaseRestoreExistingServerWithPricin Fails After 1 Hour of Trying

Mike-E-angelo 491 Reputation points
2023-05-10T22:00:07.08+00:00

I am attempting to restore an Azure Database to a point in time (today at 0:00UTC) and it fails after about an hour of trying:

{"code":"DeploymentFailed","target":"../deployments/Microsoft.SQLDatabase.newDatabaseRestoreExistingServerWithPricin","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":"/..","message":"The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'."}]}

Correlation ID: 526cdd14-9f43-4480-9fe4-eb9bf5c58473

Thank you for any assistance you can provide.

Azure SQL Database
{count} votes

2 answers

Sort by: Most helpful
  1. VasimTamboli 4,780 Reputation points
    2023-05-14T15:10:22.5133333+00:00

    The error message you provided indicates that the deployment of the Azure Database restore operation has failed. The specific reason for the failure can vary, and it would be helpful to investigate the deployment operations and error details for more information.

    To list the deployment operations and view the details, you can use Azure CLI or PowerShell commands. Here are the steps you can follow:

    Using Azure CLI:

    1. Open the Azure CLI command prompt or Azure Cloud Shell.
    2. Run the following command to list the deployment operations:
    csharpCopy code
    az group deployment operation list --name <deployment-name> --resource-group <resource-group-name>
    

    Replace <deployment-name> with the name of the deployment and <resource-group-name> with the name of the resource group where the deployment is taking place.

    Using Azure PowerShell:

    1. Open the Azure PowerShell command prompt or Azure Cloud Shell.
    2. Run the following command to list the deployment operations:
    phpCopy code
    Get-AzDeploymentOperation -DeploymentName <deployment-name> -ResourceGroupName <resource-group-name>
    

    Replace <deployment-name> with the name of the deployment and <resource-group-name> with the name of the resource group where the deployment is taking place.

    Reviewing the deployment operations should provide more detailed information about the specific failure and any error messages associated with it. This can help in troubleshooting the issue and determining the necessary steps to resolve it.

    If you need further assistance, please provide the specific error messages or any additional details from the deployment operations, and I'll be happy to help you further.


  2. Oury Ba-MSFT 17,061 Reputation points Microsoft Employee
    2023-05-22T21:11:20.4366667+00:00

    Mike-E-angelo Sorry for the delay in response to the above issue.

    I was able to check this internally and it happens that this is a known issue.

    It is recommended to retry using S3 or higher slo and then downgrade back to desired. That is the workaround as I mentioned above.

    Please let me know if you have any further questions.

    Answer to your question as why it is not mentioned in the error message you received while doing the restore. I also checked on that and a work is in progress to make the error massage more meaningful. This issue should not be happening in the future.

    Regards,

    Oury