Servers provide vital computing resources -- the processor cycles, RAM, disk I/O and network connectivity needed...
By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.
to drive critical enterprise applications. Virtualization adds a new wrinkle to server resource considerations, and data center administrators must weigh server resources against the computing needs of numerous virtual machines (VMs).
Modest consolidation projects rarely strain server resources, simply drawing from a server's underutilized computing capacity. But modern enterprise applications can pose enormous demands, easily justifying CPU, memory, and other server upgrades rather than investing in a new server outright. The onus is on IT professionals to determine adequate server resources, measure actual resource utilization of VMs, and maintain the availability of virtualized servers.
The computing needs of virtualization
To really appreciate the importance of server resources, it's important to understand how computing resources are affected by virtualization. A conventional (non-virtualized) application server typically runs at least one major enterprise application such as an email or database server. Each application demands a certain amount of processing (CPU) cycles, memory (RAM), local disk I/O and network bandwidth. In most cases, the physical server provides ample computing resources, and the application easily meets performance requirements. It's not uncommon to find non-virtualized application servers running at only 5% to 10% utilization.
Server virtualization changes the way that IT professionals need to think about computing resources. Each virtual machine added to a physical host will demand additional CPU, memory, I/O and network connectivity -- applications have the same demands that they would in a non-virtualized deployment. The demands on computing resources are cumulative, vastly increasing the server's total processing load.
The resource underutilization so commonplace in physical servers is usually a boon for virtualization, allowing multiple VMs to consume more of the available server resources that might otherwise be left idle. "The whole point of virtualization is that you drive up utilization of the things that you're spending money on," said Bob Plankers, technology consultant and blogger for The Lone Sysadmin.
However, while most servers have the available computing resources needed to accommodate additional VMs, the demands of each workload can vary considerably. For example, hosting processor-intensive workloads may strain the server's processor cycles while leaving plenty of memory and network bandwidth. Given the storage-intensive nature of virtual machines, disk I/O can often emerge as a gating factor. Data center professionals must understand the computing requirements of each workload, distribute workloads to optimize consolidation, and implement any necessary upgrades to maintain availability.
Determining the needs of virtual workloads
One of the first steps in any server consolidation project is to determine the computing resources (CPU, RAM, disk I/O, and network bandwidth) needed for each workload. This is not a difficult process -- relevant requirements can easily be determined by reviewing ongoing performance logs and baseline data for each non-virtualized server operating under normal load conditions. If baseline data is not readily available, it can be generated on live systems or approximated in a lab environment. The underlying operating system and hypervisor also require computing resources, so be sure to include those requirements in your estimates as well.
As a rule, never determine workload needs based entirely on the recommendations or anecdotal suggestions of staff. Bill Kleyman, director of technology at World Wide Fittings, a manufacturer and distributor of steel hydraulic tube and fittings headquartered in Niles Ill., noted a recent example of database programmers vastly over-specifying the needs for a virtualized database machine. "They only needed one CPU and about 2 GB of RAM, and the application is doing fine," he said.
Next, consider which workloads will be virtualized onto each physical server. This is an important step, as it is unlikely that all physical servers will be consolidated onto a single physical server. While it may be technically possible (especially for SMB environments), it is certainly not a best-practice because a single server itself presents a single point of failure -- potentially compromising all of the organization's workloads.
In actual practice, virtualized workloads are distributed across two or more physical servers. This approach offers several benefits. Data center administrators can "mix and match" the demands of each workload to the server's available resources. For example, rather than hosting two processor-intensive VMs on one server and two memory-intensive workloads on another, the VMs can usually be distributed so that a server hosts one processor-intensive and one memory-intensive workload. This also allows incompatible workloads to be kept apart and related workloads to be kept together. Multiple servers also allow for the redundant handling of critical workloads. As an example, an Exchange Server VM can exist on one server and be redundantly duplicated to another physical server through a tool like everRunVM from Marathon Technologies. If one instance of the VM fails, the redundant instance can take over seamlessly.
Remember that it's never a best-practice to "max-out" a server's resources -- always allow some amount of headroom for the server to host additional VMs if the need arises. This can occur when a hardware fault or routine maintenance demands that a particular server be taken offline. The VMs from that server can then be re-initialized (or "spun-up") from SAN storage onto the remaining servers while the affected server is repaired or maintained. Some organizations include a spare server for exactly this purpose (sometimes called an N+1 configuration). Headroom also allows for future growth demands of more or larger workloads.
Finally, once the workload and additional headroom requirements are known, it is then a relatively simple matter to add up the processor, memory, I/O, and network requirements for each workload and compare the totals to the available resources on each respective server. Any resource shortfalls can then be addressed with further workload distribution planning, appropriate server hardware upgrades, or entirely new servers.
ABOUT THE AUTHOR
Stephen J. Bigelow, senior features writer, has more than 15 years of technical writing experience in the PC/technology industry. He holds a BSEE, CompTIA A+, Network+, Security+ and Server+ certifications and has written hundreds of articles and more than 15 feature books on computer troubleshooting, including Bigelow's PC Hardware Desk Reference and Bigelow's PC Hardware Annoyances. Contact him at email@example.com.