May 31, 2022 at 9:29 am
I had a WSFC failure which left my 2016 AG out of quorum. The SQL windows hosts were restarted (by someone else). My 1 AG database was left in recovering & in order to get it working I brought it online via ALTER DATABASE xx WITH RECOVERY. Users are connecting into the AG, via the usual AGListener.
Now I have a situation whereby my "primary" box - where the db is online has a standalone. Within SSMS I cannot see the AG menus. On my "secondary" box my AG is "resolving". I cannot failover without data loss.
On the WSFC side, my AG is listed as failed & will not come online.
I'm in a bit of a pickle. Some of my own making. Some caused by issues as yet unknown. I would like to bring the AG back online & be able to reseed my database.
Any ideas gratefully received.
June 1, 2022 at 10:10 am
Thanks for posting your issue and hopefully someone will answer soon.
This is an automated bump to increase visibility of your question.
June 4, 2022 at 3:10 pm
I haven't worked with WSFC/AG for a while and I don't have access to a test system but, if I remember correctly, the WSFC cluster provides a reason why it's offline. If so then that might help?
June 19, 2022 at 7:58 am
This was removed by the editor as SPAM
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply