Here are some notes that I took as I went through to get a Windows Server 2008 R2 and SQL Server 2008 R2 cluster running on Hyper-V. Some may not be in the exact order, but I’ll try to get them in such.
1. Active Directory (AD) environment – I have an AD domain running on a server at home, so I didn’t think much about this, but it is a requirement. I have several servers, but I believe I read where someone from Microsoft actually put AD and all of the VHDs and cluster on the same box, so that is possible as well. Whatever you choose, AD will need to be working properly.
2. Create the VHDs – One thing here to remember on the o/s… both VHDs must be at the same security patch and service pack level or it won’t let you create the cluster. I went ahead and assigned static IP addresses to mine, but I always do anyway I guess for vhds.
3. iSCSI disks required – In order to have a Windows cluster and SQL cluster, you have to have shared storage. Unless you have a lot of cash, you will use a software-based solution to mimic shared drives like the rest of us. I used Storage Server 2008 for mine; I see on the web where a lot of folks use something called Starwind, but because I don’t know anything about it, I won’t recommend it or place a link to it. Needless to say, if you can’t obtain Storage Server, investigate this route.
4. Storage Server 2008 – I set this up on a dedicated server for shared storage, but I’m sure that you can put this on Hyper-V as well. It sets up fairly easily, but if you have problems with it, there is a good video from Microsoft on how to set it up. Google it, or search this blog for a link to the vid. Essentially, you will configure the iSCSI Initiator, and then set up the iSCSI targets in Server Manager as I show here in order to create virtual disks for shared storage. For mine I created a small drive for a quorum, and then three other disks. For a bare bones system for demos, I think you need the quorum and only one drive for the database files:
5. Set up disks in the VHDs – for the nodes, you will need to see the shared storage. You do this via the iSCSI Initiator app. Here’s the first tab where I have targets recognized.
From here, you won’t automatically be able to use the drives (but you can see them), so you need to go back and add and format the volumes in the storage folder of Server Manager (the old name was Disk Management), as if you added any new drive to a server or workstation.
6. Get Windows Server 2008 R2 cluster working solidly – This is the key step out of everything. If the Windows cluster isn’t working at 100%, you’ll have problems. I say this because once it’s locked down and you are getting no errors, SQL Server installs like a breeze. There are several steps here, but the wizards will guide you, and remember that the “Validate This Cluster” tool will definitely be your friend here. I dorked with my Windows Cluster for a week or so before installing SQL Server.
7. Create the MSDTC service and application – I did this before trying to install SQL Server and it went smoothly. I think you can do it while setting up SQL Server, but I suggest doing it beforehand. When you have it already set up, you can fail it over to the other machine and make sure it’s working properly. I also went ahead while I was at it and set up the file services role too.
8. By now you if you have the Windows cluster working, go ahead and set up SQL Server. It’s super easy these days – I actually did it in about 10 minutes without a book or guide. (I remember in the past having to have the 25 step guide nearby that Microsoft had for us to get the thing working…no need now). Choose one node and point to the media and add SQL Server. The wizards will guide you, and if you have IP addresses and your logins/passwords, you won’t have a problem.
9. No need to create cluster shared volumes, just leave them in Storage folder. We won’t be doing any Hyper-V migrations or moves here, just a plain old setup.
Here you can see my cluster is working just fine; the errors that I am getting due to the fact that I turn parts of my cluster off and on, and it doesn’t like this of course.
From here I can add more nodes or add more SQL Servers if I wanted to, or test it, or become more familiar with it. It’s a good way to keep your skills up, and I suggest that if you are on the SQL Admin track you’ll want a playground such as mine. As an option if don’t have access to an MSDN subscription, consider Starwind for iSCSI, and go download the 90-day vhd trials already created for you on the Microsoft site.
Thanks for reading,
Lee
--------------------------
I guess I should have used SQL Denali CTP 3…oh well.
2a22a1e7-b930-48a7-aa9a-5744ba5e0e71|0|.0