Posted by: SteveBige01
when relevant content is
added and updated.
Server consolidation is a great idea on paper – you use virtualization software to host multiple virtual machines on the same physical host, so you improve hardware utilization and buy fewer servers, right?
The problem is that many organizations just vacuum up the computing resources that consolidation is supposed to save. Everybody is clamoring for more resources. Test and dev needs to prove out some new builds, accounting wants more resources for the year-end tax season, creative needs a new version of AutoCad, and there are 20 new web servers that have to come online for the holidays. Just take a few minutes and provision the new servers; no problem.
But wait…before you know it, the servers are jammed with more VMs than anyone ever expected, and they never seem to go away. Sure, organizations can shell out cash for more servers, but the nasty little cycle just starts all over again. The space savings, the power savings, the capex savings; it all goes away. And it gets worse. All those VMs need management time and storage/backup/DR protection. I swear it’s enough to make me move to Nebraska and take up chicken farming.
So how do you handle this dilemma? Is it just a matter of putting policies and procedures into place to justify new VMs? Do you use VM lifecycle management tools to handle processes automatically? Or do you just fork over the cash for more servers and hope for the best? What tactics are working for you, and which tactics are not?