Share via

How to fix Failover problem

Milton Xavier Sarmiento 0 Reputation points
2023-09-16T17:12:02.3766667+00:00

I was trying to publish a failover database but I got this error

{
    "status": "Failed",
    "error": {
        "code": "InternalServerError",
        "message": "An unexpected error occured while processing the request. Tracking ID: 'a55eadaf-746e-4dd9-8c65-b37404647beb'"
    }
}
Azure SQL Database
0 comments No comments

1 answer

Sort by: Most helpful
  1. Nandan Hegde 36,886 Reputation points MVP Volunteer Moderator
    2023-09-16T18:14:32.1433333+00:00

    Not sure whether this is related to this aspect : Hey, can you state the region of your database? https://azure.status.microsoft/en-in/status There seems to be some outage going on which might be the cause note: Starting at 07:33 UTC on 16 Sep 2023, you have been identified as a customer using Azure SQL Database in East US who may experience issues when trying to connect to your Database. Connections to databases hosted in a subset of this region may result in an error or timeout.

    Workaround: Impacted customers with DR enabled on their database can do failover.

    Current Status: We have identified that during a brief period of time an underlying network infrastructure has suffered with power issues, resulting in a downstream impact for SQL Database in East US region. In addition, we have found some unhealthy compute nodes impacting our service on East US region as well. We are manually rebooting affected instances, which should bring the databases back online. Some signs of recovery are being observed with instances that have been rebooted. The next update will be provided in 60 minutes, or as events warrant.

    Was this answer helpful?

    0 comments No 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.