Taken from our Virtualisation with Microsoft® Hyper-V eBook (available to view and download below).
Here’s a look at a typical small scale scenario:
You are a school with only 4 servers, one of which is your Active Directory server, maybe a setup like the one below.
For this scenario you could quite easily use one server for your virtualisation host with lots of diskspace and end up reducing your servers from 4 to 2 as shown below.
While this would work and be relatively low cost to implement it does fall down in a two key areas: • Future Growth – As your needs for more servers may increase it will put more strain on the resources of this single host and ultimately this may have a detrimental effect on your end user experience. • Redundancy – If your host fails then all of your virtual servers will fail as well as all the virtual hard drives are stored on your single server. You can imagine the effect of this.
A better solution is shown below. This one gives you redundancy and the ability to grow your virtualisation environment in line with increasing needs.
So how is this scenario so much better than our first one? • Future Growth – While initially this scenario may seem like overkill what it does allow you to do is grow your environment as your needs change, without buying more equipment or completely changing your setup. • Redundancy – Because all the virtual hard drives are stored on a central storage system the failure of one host will not affect the running of your virtual servers. Failover clustering will take care of the transfer of services between hosts automatically and your users’ experience will not be affected.
You can view and download the full Virtualisation with Microsoft® Hyper-V eBook below.