Access your Pro+ Content below.
Using virtual systems management to define server ownership
This article is part of the Virtual Data Center issue of May 2009, Vol. 10
Andi Mann In deploying and managing virtualization, one of IT's most persistent problems is overcoming the political issues that come with major technological change. These issues often center on the fundamental conflict between business units and IT over which unit owns and pays for servers in a virtual data center. In this tip, I'll identify some basic virtual systems management (VSM) disciplines, such as chargeback and capacity planning, that help eliminate business-unit wrangling and enable IT to develop an approach to future service delivery. How virtualization has changed server allocation and ownership When applications moved from multi-tenant environments like z/OS, VMS and AS/400 systems, business units and department managers effectively began buying and using their own dedicated physical systems. Each business application ran on a specific server in the data center, usually sporting a distinctive label to identiy the server's purpose. Each department requisitioned its own servers, paid for them out of its budget, had ...
Access this PRO+ Content for Free!
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.
Features in this issue
If it's done right, optimizing server utilization with virtualization can save data centers money.
Business-unit squabbles over server ownership and allocation are complex in virtual environments. But using virtual systems management principles, such as chargeback and capacity planning, can help.
Virtual data backup is more complicated than you're used to. New data backup best practices, such as shared storage and snapshots, will help you meet these challenges.