![]() ![]() The first order of business when approaching a small virtualization project is to choose the hardware. Fortunately, setting up and testing these requirements beforehand isn’t difficult. It all depends on the hardware resources available to the host server, on the virtualization software features, and on the requirements of the virtual server. Some servers, such as database servers, run heavier loads on a more consistent basis, and may not be suitable candidates for virtualization in a smaller infrastructure. That isn’t a hard and fast rule, however. ![]() By taking advantage of this law of averages, you can consolidate a considerable number of physical servers onto a single host server. When they are tasked with work, their resources tend to be spread out among the RAM, CPU, disk, and network input/output, with only a subset of the virtual servers actually requiring significant CPU resources. The reason is that generally most servers run near idle a significant portion of the time. Even though this one server will be responsible for hosting possibly dozens of virtual servers, it will require far fewer CPU resources than you might assume.ĭepending on the virtualization software in use–VMware, Microsoft’s Hyper-V, Citrix XenServer, or another package–you will likely be able to run a surprising number of virtual servers on a four- or six-core CPU. The key to successfully virtualizing servers in a smaller environment starts with the physical host server, the box that will run multiple virtual servers. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |