We had small domain consisting of a Windows domain controller and two Windows 2008 R2 servers running SQL 2012. The SQL servers were part of a WSFC, and set up with a AlwaysOn Availability Group. The DC also hosted the Witness File Share.
We had a problem with the domain controller that caused it to be recreated from scratch, so it is brand new, SIDs and all.
After the failure of the DC we took steps to get one SQL server back in service so the Web servers using its services could stay up. On the primary SQL server, the AlwaysOn Availbiltiy Group was deleted. In the Web servers that used the databases, the connection strings were altered to go to the node instead of the Virtual name. There may have been some other changes, but I'm not sure. If something else is important to know, I can find out.
Today I the SQL server still providing services to the Web servers, a new domain controller, and an unused out of date SQL server that can't make quorum.
I have removed the unused SQL server from the old domain and have added it back to the new domain. (Names haven't changed but I know the SID has).
I was wondering what the steps would be to recover my systems so they are all working correctly again. When I get done, I want a SQL Server FCI (instead of using the AOAG), consisting of the two SQL servers. How do I get things cleaned up that are no good on the unused server and when can I do it? What things should I watch out for? How do I keep down time to a minimum?
The SQL server has 6 user databases that have an initial size of 5 or 6 GB each.
I'd appreciate it is anyone can provide the recovery steps for this situation. Thanks.