Our SolarWinds database exists in a VMware environment using DRS. We had a purple screen occur and a live migration caused the Primary database to be stuck in a "Restoring" state after failover to the Secondary..
This is a popular problem in the SQL world (database stuck in "Restoring" mode) and I'm just wondering if anyone has experienced this with the SolarWindsDB and your thoughts of combating this if anyone has ideas.
Now we must rebuild the AOAG config which is how we fixed it last time - re-adding the database and other shenanigans our DBA did. I'm not a DBA so perhaps there are better ways of handling this.
Thanks
