Virtualization is catching on like never before. Just about every server vendor is advocating it heavily, and IT departments worldwide are buying into the technology in ever-increasing numbers.
"The use of virtualization in the mainstream is now relatively commonplace, rather than just in development and test," said Clive Longbottom, an analyst at U.K.-based Quocirca. "In addition, business continuity based on long-distance virtualization is being seen more often."
As a result, the time has come to more closely align hardware purchasing with virtualization deployment. So what are some of the important do's and don'ts of buying servers and other hardware for a virtual data center infrastructure? What questions should IT managers ask before they make selection decisions on servers? And how should storage virtualization gear be integrated into the data center?
Do's and Don'ts
There are, of course, plenty of ways to virtualize, depending on the applications being addressed. This article will focus on a typical case where infrastructure and business logic applications are the main targets.
With that in mind, one obvious target is memory. It is a smart policy to buy larger servers that hold more memory to get the best return on investment. While single- and dual-processor systems can host multiple applications under normal circumstances, problems arise when two or more hit peak usage periods.
"Our field experience has shown that you can host more VMs [virtual machines] per processor and drive higher overall utilization on the server if there are more resources within the physical system," said Jay Bretzmann, worldwide marketing manager, System x at IBM (Armonk, N.Y.). "VMware's code permits dynamic load balancing across the unused processor resources allocated to separate virtual machines."
|Smart IT Articles|
Virtualization Services Market, 2007-2011 Forecast
Virtualization: A Primer
Virtualization: Xen vs. Microsoft vs. VMware
Will Virtualization Doom Server Sales?
He advised buying servers with more reliability features, especially those that predict pending failures and send alerts to move the workloads before the system experiences a hard failure. Despite the added cost, organizations should bear in mind that such servers are the cornerstone of any virtualization solution. Therefore, they deserve the lion's share of investment.
"Businesses will lose significant productivity if the consolidation server fails," said Bretzmann. "A hard crash can lead to hours of downtime depending upon what failed."
Longbottom, however, made the point that an organization need not spend an arm and a leg for virtualization hardware as long as it doesn't go too low end.
"Cost of items should be low these items may need swapping in and out as time goes on," said Longbottom. "But don't just go for cheapest kit around make sure that you get what is needed."
This best achieved by looking for highly dense systems. Think either stackable within a 19-inch rack or usable as a blade chassis system. By focusing on such systems, overall cooling and power budgets can be better contained. Remember, too, not every server is capable of being managed in a virtual environment. Therefore, all assets should be recognizable by standard systems management tools.
Just as there are things you must do, several key don'ts should be observed as well. One that is often violated is that servers should not be configured with lots of internal storage.
"Servers that load VMs from local storage don't have the ability to use technologies like VMotion to move workloads from one server to another," cautioned Bretzmann.
What about virtualizing everything? That's a no-no, too. Although many applications benefit from this technology, in some cases, it actually makes things worse. For example, database servers should not be virtualized for performance reasons.
Support is another important issue to consider.
"Find out if the adoption of virtualization will cause any application support problems," said Bretzmann. "Not all ISVs have tested their applications with VMware."