Virtual Desktop Patching and Data Protection

Data Protection and patch management of virtual desktops, while not a sexy topic, is one that should happen on a regular basis within any organization implementing or working to implement virtual desktops. Recently, we have been testing virtual desktop software and there is a huge difference between patching and protecting data in a small number of instances and 1000s of instances. There are scale considerations as well as ease of use for file level and system recovery as well as issues with patching virtual desktops (not to mention other security issues).

OpenStack and the Software Defined Data Center (SDDC)

The future of OpenStack looks bright, and with the all the software-defined data center (SDDC) features contained in the recent release of “Grizzly” they are now ready to compete toe-to-toe with heavyweights like VMware, Nutanix, Dell, and HP. Whether they can start unseating VMware products in the enterprise remains to be seen, though. Despite the immediate SDDC advantage of OpenStack, companies and technologies like that of Nicira and Virsto, both acquired by VMware, are not to be ignored.

A Look at the HP Moonshot 1500

Last week HP announced their “second generation” HP Moonshot 1500 enclosure and Intel Atom S1260-based Proliant Moonshot systems, a high-density computing solution targeted at hyperscale computing workloads. They’re billing it as the first “software defined server” and claiming that it can save 89 percent of energy, 80 percent space, and 77 percent of the cost of their DL380 servers.

Caching throughout the Stack

One sure way to improve performance is to cache the non-dynamic data of any application. We did this to improve the overall performance of The Virtualization Practice website. However, there are many places within the stack to improve overall performance by caching, and this got me to thinking of all the different types. At the last Austin VMUG, there were at least three vendors selling caching solutions that were designed to improve overall performance by as little as 2x to upwards of 50x improvements. That is quite a lot of improvement in application performance. Where do all these caching products fit into the stack?