Need to P2V a SQL cluster at work. Here’s screenshots of what I did in a test environment to see if an idea of mine would work.
We have a 2 physical-nodes SQL cluster. The requirement was to convert this into a single virtual machine.
P2V-ing a single server is easy. Use VMware Converter. But P2V-ing a cluster like this is tricky. You could P2V each node and end up with a cluster of 2 virtual-nodes but that wasn’t what we wanted. We didn’t want to deal with RDMs and such for the cluster, so we wanted to get rid of the cluster itself. VMware can provide HA if anything happens to the single node.
My idea was to break the cluster and get one of the nodes of the cluster to assume the identity of the cluster. Have SQL running off that. Virtualize this single node. And since there’s no change as far as the outside world is concerned no one’s the wiser.
Found a blog post that pretty much does what I had in mind. Found one more which was useful but didn’t really pertain to my situation. Have a look at the latter post if your DTC is on the Quorum drive (wasn’t so in my case).
So here we go.
1) Make the node that I want to retain as the active node of the cluster (so it was all the disks and databases). Then shutdown SQL server.
2) Shutdown the cluster.
3) Remove the node we want to retain, from the cluster.
We can’t remove/ evict the node via GUI as the cluster is offline. Nor can we remove the Failover Cluster feature from the node as it is still part of a cluster (even though the cluster is shutdown). So we need to do a bit or “surgery”. :)
Open PowerShell and do the following:
|
1 2 |
Import-Module FailoverClusters Clear-ClusterNode –Force |
This simply clears any cluster related configuration from the node. It is meant to be used on evicted nodes.
Once that’s done remove the Failover Cluster feature and reboot the node. If you want to do this via PowerShell:
|
1 2 3 |
Import-Module ServerManager Remove-WindowsFeature FailoverClustering Restart-Computer –Force |
4) Bring online the previously shared disks.
Once the node is up and running, open Disk Management and mark as online the shared disks that were previously part of the cluster.
5) Change the IP and name of this node to that of the cluster.
Straight-forward. Add CNAME entries in DNS if required. Also, you will have to remove the cluster computer object from AD first before renaming this node to that name.
6) Make some registry changes.
The SQL Server is still not running as it expects to be on a cluster. So make some registry changes.
First go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\Setup and open the entry called SQLCluster and change its value from 1 to 0.
Then take a backup (just in case; we don’t really need it) of the key called HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\Cluster and delete it.
Note that MSSQL10_50.MSSQLSERVER may vary depending on whether you have a different version of SQL than in my case.
7) Start the SQL services and change their startup type to Automatic.
I had 3 services.
Now your SQL server should be working.
8) Restart the server – not needed, but I did so anyways.
Test?
If you are doing this in a test environment (like I was) and don’t have any SQL applications to test with, do the following.
Right click the desktop on any computer (or the SQL server computer itself) and create a new text file. Then rename that to blah.udl. The name doesn’t matter as long as the extension is .udl. Double click on that to get a window like this:
Now you can fill in the SQL server name and test it.
One thing to keep in mind (if you are not a SQL person – I am not). The Windows NT Integrated security is what you need to use if you want to authenticate against the server with an AD account. It is tempting to select the “Use a specific user name …” option and put in an AD username/ password there, but that won’t work. That option is for using SQL authentication.
If you want to use a different AD account you will have to do a run as of the tool.
Also, on a fresh install of SQL server SQL authentication is disabled by default. You can create SQL accounts but authentication will fail. To enable SQL authentication right click on the server in SQL Server Management Studio and go to Properties, then go to Security and enable SQL authentication.
That’s all!
Now one can P2V this node.