News
1/10/2011
12:55 PM
George Crump
George Crump
Commentary
Connect Directly
RSS
E-Mail
50%
50%

Desktop Virtualization And Local Storage - Just Say No

There is an ongoing debate about what type of storage is best to use to support desktop virtualization solutions, especially in small to medium sized implementations. Storage is one of the most expensive parts of a desktop virtualization project and as a result anything you can do to drive cost out of the storage purchase is going to make desktop virtualization economics work better. This leads some to advocate local storage.

There is an ongoing debate about what type of storage is best to use to support desktop virtualization solutions, especially in small to medium sized implementations. Storage is one of the most expensive parts of a desktop virtualization project and as a result anything you can do to drive cost out of the storage purchase is going to make desktop virtualization economics work better. This leads some to advocate local storage.The theory goes that local storage is going to be a less expensive and an easier to implement solution for the virtual desktop project. At the surface those are valid points but when you weigh what you give up by not going to shared storage and how you have to configure local storage to provide users with a respectable desktop experience I'm not sure if local storage is quite the deal it sounds like.

First let's look at what you have to do to local storage to get it ready for desktop virtualization. From a performance perspective you are going to need enough drives to generate enough IOPs to provide adequate performance to those now virtualized desktops. While the typical working IOPs requirement of a virtual desktop is relatively light, typically less than 5 IOPs. However the per virtual desktop IOP during boot up, logon/logoff, software update operations that number can increase substantially, as much as 5X. As we discuss in our recent article "Solving Boot Storms With High Performance NAS" these activities are the real challenge in the environment and something that needs to be planned for when designing the storage system.

Providing your virtual desktop environment with high performance and highly reliable storage is not as simple as running down to your local computer store and picking up that $99 2TB hard drive. You're going to want something a little more enterprise class with a 15K RPM speed. Most environments will either use RAID 1 or RAID 5 for data protection so that will require a more expensive controller to be purchased and the protection overhead will eat into performance. The need for performance and reliability is typically going to require an eight to ten drive RAID configuration. This drive count is going to be beyond the internal drive capability of most servers, which means an external storage system.

The combination of faster drives and an external chassis erodes some of the price advantage compared to mid-range storage systems but not all of it. Its the limits of locally attached systems in this type of configuration that become the real challenge. Most price competitive external systems can only be expanded so far. As you add virtual desktops you may need additional external systems, which adds to the cost and to complexity.

As we discussed in our webinar "Making Sure Desktop Virtualization Won't Break Storage" there is some planning required vs local storage. That planning though is often worth what you gain from shared storage. The big give up with local storage is that you loose much of what desktop virtualization brings like virtual machine migration and server balancing. You need shared storage to be able to migrate machines and balance load. You also give up the ability to offload from the hypervisor all the things that shared storage does well like scalability, snapshots, cloning, deduplication and replication. While its true that some of these functions can be performed via software all of those come at an added cost of not only dollars but also server resources. Finally shared storage can be leveraged for other storage uses, like server virtualization, as well so the cost of the shared storage investment can be allocated across several projects.

Local storage may have a roll to play in desktop virtualization but you have to weigh all the odds. Is desktop virtualization without shared storage really going to give you a return on the investment? If you factor everything in, you may be better off getting shared storage first and then deploying virtual desktop later than you would be to live with an virtual desktop project that under achieves due to poor storage performance. One thing we have seen consistently is once users get a bad taste for virtual desktop, they rarely will give it a second chance.

Track us on Twitter: http://twitter.com/storageswiss

Subscribe to our RSS feed.

George Crump is lead analyst of Storage Switzerland, an IT analyst firm focused on the storage and virtualization segments. Find Storage Switzerland's disclosure statement here.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Flash Poll
Current Issue
Cartoon
Threat Intel Today
Threat Intel Today
The 397 respondents to our new survey buy into using intel to stay ahead of attackers: 85% say threat intelligence plays some role in their IT security strategies, and many of them subscribe to two or more third-party feeds; 10% leverage five or more.
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-6306
Published: 2014-08-22
Unspecified vulnerability on IBM Power 7 Systems 740 before 740.70 01Ax740_121, 760 before 760.40 Ax760_078, and 770 before 770.30 01Ax770_062 allows local users to gain Service Processor privileges via unknown vectors.

CVE-2014-0232
Published: 2014-08-22
Multiple cross-site scripting (XSS) vulnerabilities in framework/common/webcommon/includes/messages.ftl in Apache OFBiz 11.04.01 before 11.04.05 and 12.04.01 before 12.04.04 allow remote attackers to inject arbitrary web script or HTML via unspecified vectors, which are not properly handled in a (1)...

CVE-2014-3525
Published: 2014-08-22
Unspecified vulnerability in Apache Traffic Server 4.2.1.1 and 5.x before 5.0.1 has unknown impact and attack vectors, possibly related to health checks.

CVE-2014-3563
Published: 2014-08-22
Multiple unspecified vulnerabilities in Salt (aka SaltStack) before 2014.1.10 allow local users to have an unspecified impact via vectors related to temporary file creation in (1) seed.py, (2) salt-ssh, or (3) salt-cloud.

CVE-2014-3587
Published: 2014-08-22
Integer overflow in the cdf_read_property_info function in cdf.c in file through 5.19, as used in the Fileinfo component in PHP before 5.4.32 and 5.5.x before 5.5.16, allows remote attackers to cause a denial of service (application crash) via a crafted CDF file. NOTE: this vulnerability exists bec...

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Three interviews on critical embedded systems and security, recorded at Black Hat 2014 in Las Vegas.