Please pardon my ignorance here concerning Hyper-V. There are tons of differing opinions/instructions on the net, which does nothing but add to my confusion. I know this is lengthy, but hopefully, when solved, it will help other “newbies!”
I have a new high power server that I have plenty of time to play with before I put it into production. It is going to replace a SBS 2008 box that is currently a DC/File/Print Server on a 30+ workstation network. The new server: Dual 2.5 GHz. Processors, 128 GB ram, 6 hot swap drives (2 x 350 GB (RAID 1) and 4 x 1.2 TB (RAID 6)), 2 Dual Port NICs, redundant hot swap power supplies, etc.
My original setup on this machine was the OS (Server 2012 R2) was on RAID 1, performing AD/DC/DHCP/DNS functions and the RAID 6 drives were for data, roaming profiles, user files, mail PST’s, etc. Basically, a glorified desktop with plenty of punch and redundancy. KISS!
Initially, using the GUI, I had all the bells and whistles installed. All 3rd party software (Dell OpenManage, Symantec Backup Exec, WSUS, Antivirus, etc.) seemed to cooperating nicely with the OS. All OS updates and patches had been applied. Being on a 350 GB drive, there was plenty of room to spare. I have since experimented with removing the GUI and using PowerShell, but it’s a nice feature to be able to switch back and forth.
One of the primary programs I need however is SQL Server (2014). It will be hosting back ends of two large databases. Both get lots of read/write activity. Here is where my problems began. Turns out that Microsoft Best Practices recommend against installing SQL on a DC. This forced me to seek alternate installation options and hence, Hyper-V!
At this point, I knew nothing of Hyper-V and was suddenly thrust into its clutches! I posted an earlier question in this forum concerning this issue. It was recommended that I create two virtual machines. One, to act as AD/DC and the other to host SQL. This, at the time, seemed logical and I set out to create my 1st Hyper-V machine. Once done, I installed the same OS and began experimenting with the myriad of configuration options. How much disk space to allocate? Memory? Can it access the data drive? Where (host or guest) do the 3rd party software programs get installed? The questions began to mount, resulting in a sleepless night!
Here’s where I need a guiding hand and expert’s opinion! Since this will be a single server network, my thinking has now come full circle. I’m back to KISS! Is it feasible to have the host machine as my DC/AD as explained in my original glorified desktop setup plan? Then, create a Hyper-V guest, install the same core OS that will host SQL? If so, do I need to consider partitioning the OS and/or DATA drives?
This seems to me, for a single server solution, a logical deployment plan. However, if you disagree, or have a better, more efficient solution, your comments, suggestions, instructions, links, etc. are greatly appreciated! Is there a step by step for my particular scenario (for dummies) anywhere? Currently, the server sits idle awaiting further research! The core OS is installed on RAID 1, single partition and the RAID 6 DATA drive is initialized and formatted on a single partition. The OS is a clean install, with no updates applied. Like I said, I have plenty of time to “play!”