Taylor Allis asked this question on his most recent blog post: “What is server virtualization’s impact on Storage?”  Here’s my opinion. But I’m interested in yours, too.

First, I think storage comes out of the server and into a shared pool. Some might say that’s a book-of-duh comment, but given the enormous storage capacity you can put inside a server today, why would anyone need to go external? Here’s the reasoning.  Server workload, virtual or not, is relatively independent of the storage workload.  By that I mean, running out of server resources to support an application has no implicit or explicit relationship to running out of storage resources (capacity or performance) to support that application.  If you need to move a virtual server from one physical server to another, because the physical server is running out of head room, there’s no explicit reason I should also have to move the data. There are some impediments, like unwanted down time, to moving data out of a server and into a shared pool, but one of our clients, StorMagic, has pretty much solved that problem with their non-disruptive data migration capabilities.

Second, I think server virtualization drives the need for end-to-end server and storage reporting and monitoring tools.  When you’ve got virtualized servers and shared, networked storage supporting production applications, how can you tell if the degraded performance that application owners are experiencing is the result of CPU resources, I/O issues, or storage capacity and performance issues?  How can you avoid performance issues altogether?  How can you decide which applications you can safely put on virtual servers and shared storage and still meet service level agreements?  Another client of ours, Tek-Tools, has pretty much figured that one out with their Profiler for VMware module.

Other implications for storage include a need for higher reliability, availability, and more scalable performance from the storage system.  That’s in response to the more-eggs-in-one-basket concern when multiple applications share a single storage pool.

OK, time for a dialogue - or blogalogue.  What are your thoughts?