I recently have been in front of a few customers discussing various designs for application and desktop virtualization. Inevitably, or at some point, we discuss storage. When it comes to storage I often pause and read the room because most people i know on the VAR and customer side have their favorites and have what I would refer to as a Dallas Cowboys team (I’m an Eagles fan, if you are a Dallas fan, just reverse the teams, it’ll work).
I’ve architected (is that a real word?) large deployments involving multiple datacenters, high availability and disaster recovery. My focus isn’t on what is the single best technology and gluing things together, it’s about what works (and hopefully, what works well). Storage can be a very big issue with VDI, traditional SAN-based storage was not designed for desktop workloads and we’ve been oblivious to faster disk speeds and low latency on drives that hum under our wrists when typing. Moving these workloads to the data center doesn’t always work and when you add in latency from a server reaching out to a separate SAN, it compounds the problem.
The traditional SAN isn’t usually the best fit for heavy desktops and applications, however, adding flash technology to the mix often deals with the IOPs issue and latency can be minimized. Is flash necessary? Nope. I’ve had designs involving 15K SAS drives local to blades work very well. The Citrix stream to memory, overflow to disk can perform even better with 10k or 7k drives. However, I often don’t get to position that solution which brings me back to my first point…everyone has favorites.
I can take almost any storage and find a solution. Even a traditional SAN, if I can use memory to cache, I can make that work. Local disk? Easy. Flash appliances, they are great! But there is one thing I’m hearing that I don’t need. The storage providing high availability or five nines. There is a simple reason I don’t need five nines and I cringe when I hear others use it and lean back.
Your application doesn’t solely rely on storage to be available!
How will five nines prevent downtime when your hypervisor crashes or profile corruption occurs? What about a failed backup on SQL that just eats up disk space? What should we do?
We need to embrace failure and assume things fail. It’s so much cheaper than having the hardware give you a warm fuzzing feeling. When that business app fails, the business doesn’t care whether it’s storage or a cleaning person tripping over a server cord (I hope that isn’t even possible in most of your environments!). They see IT as the failure, not storage.
I wish I could take credit for this thought process but netflix has pretty much perfected this thought. If you haven’t heard of the chaos monkey you should learn – http://techblog.netflix.com/2012/07/chaos-monkey-released-into-wild.html .
Spend enough time in IT and you’ll realize that chaos always wins and you burn out quick if you’re fighting it. However, returning to my original point, the design and architecture can do this also. When we talk of desktops, many argue persistent versus non-persistent. Persistent means you keep your desktop, non-persistent means you can roam (which usually means some flavor of roaming profiles). I’m a big advocate of non-persistent. Your storage or server fails, you get logged off, you log back in and you’re right where you were (or very close to it). If the application is database driven and supports mirroring, you can survive storage failures, if setup correctly.
Going back to storage, this means two of whatever I have. Two local drives, two appliances, two SANs. I’ll take two 95% up-time appliances over a single 99.999% appliance anytime. I’d rather save costs with single controllers than try to make a single point of failure not fail (because your application never has a single point of failure, it’s got multiple points of failure).
I’m not arguing five nines doesn’t have a place somewhere. If you can’t use non-persistent, it might be for you. However, I’d argue that virtualizing your applications and desktops is not a good move if you need persistence anyways. Just my two cents, feel free to comment if you agree, disagree or think I’m full of it, I’m always open to suggestions!
PS – This is a first draft to publish, I’m sure there some typos and run-on sentences in there.