Windows Server 2012 R2 OEM, Hyper-V & Disaster Recovery
I need to ask a question about new Dell Server T320 that was purchased with Windows 2012 R2 OEM. This server will be used at a small office with about 5 users that use both MAC and PCs that will connect to this new server. I am wanting to use this server as a hypervisor to host one VM and allow another for any future expansion. This server has 1TB of usable space. This office does not have the funds for a NAS, so all the data will reside in each VM. I believe we are looking around 200-300Gbs of initial user data that will be stored on the server. It will grow over time, and I cannot so how fast but I would not think dramatic growth. This a new client that was taken on as of last week.
Anyway, I noticed Windows Server 2012 R2 is an OEM version and not a MS VOL license. So, I am just trying to think of any possible disaster recovery scenario that could possibly happen. If there was a need to move the VM to another physical hypervisor will I have problems with the OEM license? If the new server has available VM licenses then can a license be applied/converted on the moved VM with OEM server license? I am hoping after moving the VM(s) between servers, and when it spins up will it will allow me to apply an available license.
I also wanted to know if I can have the VM setup with one drive (C:) that will house the OS and user files and a lightly used SQL express database, or attach a drive to the VM to house the user data and SQL database? Not sure if it matters, but I thought I'd ask. I was thinking one drive to hold everything for each VM, and if more space is need I would simply expand the drive as necessary.
Another thing, when the server was purchased it only has dual NICs. I understand one physical NIC will be reserved for the HyperVisor, but how will two VMs use the Remaining NIC? Can I setup the first VM using the second physical NIC, and then setup the second VM with some sort of virtual NIC or do I need purchase another physical nic altogether?
One final question, I need to know how USB drives connect to VMs. What I mean is, I will install security software for managing access to doors that requires the use of a USB dongle that must be attached to the VM. So, can I assign a specific USB drive to a specific VM? The dongle must remain attached at all times.
Anyway, I noticed Windows Server 2012 R2 is an OEM version and not a MS VOL license. So, I am just trying to think of any possible disaster recovery scenario that could possibly happen. If there was a need to move the VM to another physical hypervisor will I have problems with the OEM license? If the new server has available VM licenses then can a license be applied/converted on the moved VM with OEM server license? I am hoping after moving the VM(s) between servers, and when it spins up will it will allow me to apply an available license.
I also wanted to know if I can have the VM setup with one drive (C:) that will house the OS and user files and a lightly used SQL express database, or attach a drive to the VM to house the user data and SQL database? Not sure if it matters, but I thought I'd ask. I was thinking one drive to hold everything for each VM, and if more space is need I would simply expand the drive as necessary.
Another thing, when the server was purchased it only has dual NICs. I understand one physical NIC will be reserved for the HyperVisor, but how will two VMs use the Remaining NIC? Can I setup the first VM using the second physical NIC, and then setup the second VM with some sort of virtual NIC or do I need purchase another physical nic altogether?
One final question, I need to know how USB drives connect to VMs. What I mean is, I will install security software for managing access to doors that requires the use of a USB dongle that must be attached to the VM. So, can I assign a specific USB drive to a specific VM? The dongle must remain attached at all times.
Last Comment
ASKER
So there is no way to export and import the OEM VM to another host, and maybe have it issue a license then, hah? So if you're absolutely sure I can't transfer the VM then what are my options?
The Hyper-V host will only be used as a hyper visor only. So I am good with that. I was referring to the two VMs as windows servers holding data.
I thought hyper-v offered virtual nics. Since I will have dual nics do you recommend teaming them on the hyper visor?
I found the following article on how to handle using usb drives for hyper-v VMs.
http://woshub.com/how-to-connect-a-usb-drive-directly-to-a-hyper-v-vm/
As far as the virtual partitions, you're saying use a virtual partition for the VM OS, and then attach another drive (let's say D:) to that VM to house SQL and user files, right? That's what I was going to do, but not sure of the best practice.
The Hyper-V host will only be used as a hyper visor only. So I am good with that. I was referring to the two VMs as windows servers holding data.
I thought hyper-v offered virtual nics. Since I will have dual nics do you recommend teaming them on the hyper visor?
I found the following article on how to handle using usb drives for hyper-v VMs.
http://woshub.com/how-to-connect-a-usb-drive-directly-to-a-hyper-v-vm/
As far as the virtual partitions, you're saying use a virtual partition for the VM OS, and then attach another drive (let's say D:) to that VM to house SQL and user files, right? That's what I was going to do, but not sure of the best practice.
As far as the virtual partitions, you're saying use a virtual partition for the VM OS, and then attach another drive (let's say D:) to that VM to house SQL and user files, right? That's what I was going to do, but not sure of the best practice.
Yes, definitely best practice.
Attaching USB DRIVES can be jury-rigged. You could potentially use pass-through for them OR create a VHD on one... but that can get messy and they are not nearly as "easily" removed. You were talking about a USB dongle - this is NOT a virtual drive.
Hyper-V takes all avaliable NICs and allows you to assign them to a VM (the Host *IS* technically a VM - the Parent VM). You can then use that NIC multiple times. Unless you're staff is editing video over the network or accessing a SAN I wouldn't bother with NIC teaming. If you have two NICs, you can definitely split them up two for one, one for the other... one for host, one for VMs, etc. With 5 users, I wouldn't expect performance to be an issue (assuming these are at least 1Gb NICs) in an environment that small.
Re: licensing - the VMs can be moved *IF* you get a volume license. If it's an OEM license, you cannot move them until you have a volume license.
Licensing is a legal issue - we cannot help you violate licensing (or encourage it). Further, as a legal issue, I cannot promise you that laws in your geographic area might not nullify aspects of what I understand - you need to contact the license granting authority to confirm ANY advice regarding licensing offered here... "I was told on Experts-Exchange" will not be a valid excuse with an Audit.
ASKER
I will contact the vendor about the USB dongle.
I plan on using one physical NIC for the host, and the physical NIC for the VMs.
Reference licensing, the error of ordering OEM was my fault. I placed the order yesterday, and while reviewing again this morning I realized it was OEM. I just contacted my Dell Sales Rep, and canceled the order. A new order will arrive shortly with a $200.00 increase for the MS VOL licenses. I let the owner know about it, and he was fine with it.
I plan on using one physical NIC for the host, and the physical NIC for the VMs.
Reference licensing, the error of ordering OEM was my fault. I placed the order yesterday, and while reviewing again this morning I realized it was OEM. I just contacted my Dell Sales Rep, and canceled the order. A new order will arrive shortly with a $200.00 increase for the MS VOL licenses. I let the owner know about it, and he was fine with it.
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Lee was very helpful. I was glad he was able to answer all my questions. Thanks for all your help Lee.
In an OEM setting, the host OS is bound to the hardware.
The guest OS environments are not. As long as the destination host has the appropriate license in place the VMs can be moved. I think the limit is 90 days per move iirc.
I can dig up the references, but the above is accurate.
EDIT: Found it: OEM Licensing.
The guest OS environments are not. As long as the destination host has the appropriate license in place the VMs can be moved. I think the limit is 90 days per move iirc.
I can dig up the references, but the above is accurate.
EDIT: Found it: OEM Licensing.
Windows Server 2012
Windows Server 2012 is the server version of Windows 8 and the successor to Windows Server 2008 R2. Windows Server 2012 is the first version of Windows Server to have no support for Itanium-based computers since Windows NT 4.0. Windows Server 2012, now in its second release (Windows Server 2012 Release 2) includes Foundation, Essentials, Standard and Datacenter, and does not support IA-32 or IA-64 processors.
21K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
There is debate about what you can and cannot do with the Hyper-V host *IF* you only have one VM. You need to get in writing a statement from Microsoft indicating what is permitted. I don't think you can do ANYTHING with the host OTHER THAN Hyper-V role and related features (not other roles). Further, I would not recommend doing anything with the host EVEN IF it were licensing permitted.
You don't need to dedicate a NIC for anything - the host and all VMs can share one. Or you can assign one per VM. Or assign one to the host and all VMs share another. Or have one dedicated to a VM and the other shared by the host and a different VM. It doesn't matter. Except for performance... but in a 5 user environment, I would find it highly unlikely anyone would ever notice an issue in that area.
As for USB, it's very simple. Hyper-V doesn't support USB. If you have a dongle, you need to contact the software maker and ask them how they work on virtualized servers and specify you are using Hyper-V (it might simply NOT). Otherwise, you might have to look at another alternative for the software.
In my opinion NEVER, EVER, do anything with C: other than the OS and program installations. Databases, user files, etc should be on another volume (say, D:). When creating D: DO NOT partition a single virtual hard drive; setup TWO virtual hard drives, one for C: and one for D: