October 2, 2014 at 2:47 pm
We have a SQL Server 2012 SP1 AlwaysOn Availability Group that distributes a database from one primary server to four secondary servers. Two of those servers are Azure VM's. In the past week we have been experiencing storage issues in the VM's where the drives just go missing and in the error log it just says, "Disk <#> was surprised removed". The drives and data files going missing will obviously do bad things to the secondary database, in this case setting the database as 'Suspect' when the drives come back online.
We have a ticket and RCA going with the Azure team right now, but this brought up the question: How do we handle a secondary database that is Suspect? Is doing a Full Sync the only way?
Thanks!
October 3, 2014 at 3:06 am
Re-do the secondary from a fresh backup
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
October 3, 2014 at 1:21 pm
That is how we are moving forward, but wasn't sure if there was any other way to resolve this since the database is more than 2TB so restoring to Azure is not always simple.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply