Koldov Posted April 18, 2016 Posted April 18, 2016 Hi All, If this thread is better off in the server forum please feel free to move... I am a complete novice to virtual machines, but I'm hoping for some sound advice. I would like to look at virtualising servers, but don't even know where to start, so I'd like to know if anybody can advise on the following points: 1 - Software to accomplish the task as there seems to be a few options, hopefully something built in or an MS download (aka free) to keep support options to a minimum as I'm running 2012R2. 2 - Hardware limitations and minimum recommended specifications - I seem to remember the spec for our most recent physical Dell server had some options for virtualisation, but I skipped them as it was not even on the horizon for us then (a few years ago) - and the added cost was prohibitive - so wonder if this means I cannot virtualise. 3 - Licensing (is there provision for a VM in a standard server license?). 4 - Links to beginners guides (as in 'for dummies'). I have no specific applications to virtualise, however I seem to think that it's about time I looked at it for things like disaster recovery, splitting up roles etc. Thanks in advance. Kol.
Steve21 Posted April 18, 2016 Posted April 18, 2016 Use HyperV as it's free/cheap if you have OVS etc. (Ignore all those Dell options for VMWare unless you have wads of cash about) There's MS programs like: https://technet.microsoft.com/en-gb/sysinternals/ee656415.aspx?f=255&MSPPError=-2147217396 to help with converting physical to virtual Licensing Wise - Standard includes HOST + 2 VMs, or Use DataCentre which is unlimited VMs Steve Programs 1
mthomas08 Posted April 18, 2016 Posted April 18, 2016 +1 for HyperV. We use it here and used at previous places. Does what it says on the tin and the GUI is very easy to setup, maintain and do what you want. Server Spec - it really depends what you plan on putting on it. I tend to aim for the stars because of any additional systems/developments can be done. 2x Intel processors (good ones), plenty of RAM and HD space - the final two are really essential for plenty of VMs. We currently have 7 servers on ours and still a bit of room for future usage. 1x DC 1x Data Storage 1x Print System 1x Virus Protection Management 1x Imaging System 1x Software Deployment Server 1x XiBo 1x Testing new OS's etc 1x RDP Server Testing We used it for any temp builds while we upgraded other servers so there was no down time that the users noticed. Future planning we have a few more in the next 1-2 Years that we plan on switching to the Virtual Server. Our next server purchase if we don't go Cloud based will also be virtualised which allows us better redundancy and so far in my experience the failures have caused barely to no downtime. 1
Koldov Posted April 18, 2016 Author Posted April 18, 2016 (edited) Well, as it's going to be my first foray into virtualisation and it really is just for testing out its merit, plus there is no money to upgrade.... I'm thinking of using the old print server (rather than messing with the more powerful main server that has SIMS and holds FMSO roles ): Obviously not amazing specs (and I'm sure we all have PC's at home that blow this out of the water), but I'd like to know if it can be done and if I could run anything worthwhile on it? I'm really only looking for 1 or 2 VM's that might hold something like SCCM, or like you have: 1x Virus Protection Management 1x Imaging System 1x Software Deployment Server 1x RDP Server As I am new to most of these too and have an innate fear of messing with production servers... Would just be nice to have something I can wipe and restart if I mess up! Kol. Edited April 18, 2016 by Koldov
Julian Posted April 18, 2016 Posted April 18, 2016 Please find below some of my thoughts about virtualisation You can use either VMware or Hyper V. VMware is more mature, Microsoft catching up rapidly, and Hyper-V comes with Server 2012r2 When virtualising servers, the number of servers greatly increases, I am running a server for just one application, this makes sure that application X will not fight with application Y. (we went from 5 physical servers to 26 virtual servers). Creating a new virtual machine is easy, useful for testing. Server 2012R2 Data Centre edition is expensive, but allows for unlimited virtual clients (per host). Server specification, we have 128 GB memory, 2 * 6 core processors, (with hyper threading) - 24 logical processors / host. Your serves are the heart of your network, if they die so does the network, it is worth paying to get good kit. 1
Steve21 Posted April 18, 2016 Posted April 18, 2016 Yeah no reason you couldn't. Obviously depends what you want on it, but could easily have a few servers running with dynamic RAM etc. Most of our things like say web-server etc only generally tick about 1GB Steve 1
Koldov Posted April 18, 2016 Author Posted April 18, 2016 Thanks all! Some stuff to think about, guess it's just a case of rolling up my sleeves and getting dirty then! Will install the Hyper-V role tonight and start messing with it. Anything to watch for in the set-up? Kol.
mavhc Posted April 18, 2016 Posted April 18, 2016 By default HyperV will only assign one vCPU per VM. Started a new job, found an 8 core machine with 2 VMs, each with only one vCPU.
Koldov Posted April 18, 2016 Author Posted April 18, 2016 Hmmmm... My little E5620 is only 4 core anyway (shows up as 8 "CPU's" in resource monitor though). Not sure what to allocate there? Also, do I need a separate partition or does it all get lumped in on the C ?
mavhc Posted April 18, 2016 Posted April 18, 2016 Probably go 2 vCPU for each VM. I'd have a boot SSD, and then the VMs on another raid. Main issue is making sure virtual drives that are expandable don't fill the space. Other issue is monitoring memory, built in stuff isn't great, need to use performance counters, https://blogs.technet.microsoft.com/chrisavis/2013/03/06/monitoring-dynamic-memory-in-windows-server-hyper-v-2012/ 1
Julian Posted April 20, 2016 Posted April 20, 2016 It is usually recommended that the host machine has multiple network connectors, 1 reserved for managing the host, the other(s) for the virtual machines. If you are using vlans, then you need a virtual switch, to send the different vlans, to the different clients.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now