A client sent a request out today letting me know that their Lync databases had failed over automatically to their mirror, but they couldn’t get them fully failed back. They were receiving the error “Database mirroring has been disabled by the administrator for database rgsdyn”. You can see this error below as I try to fail this single database back.
Sure enough, connecting to SQL Manager proved that mirroring was disabled. Oddly, this database was the only one that wasn’t failing over. As you can see from the screenshot below, the mirror is marked as suspended. A quick review of the SQL logs showed that a failure two weeks prior kept the primary down for an brief amount of time, this outage caused the mirror to suspend itself.
In our case the database and logs were healthy enough on both sides that we could restart the mirror. I used the GUI to navigate open the properties of rgsdyn on the primary copy (which is on our secondary SQL server now), navigate to Mirroring, and click the Resume button.
Mirroring went right back to a healthy state.
And I was able to re-run my command without issue to bring all copies back to our main SQL server without error.
For those who aren’t so lucky, mirroring may need to be rebuilt for the database in question. Of course the real issue at hand is why the virtualization environment isn’t more stable.