Part 4 of a 5-part series based on my more than a decade of virtualization experience with large enterprises and service providers, and my time running strategic planning for one of the largest 2 virtualization vendors, this blog series covers 10 types of situations when you should consider not virtualizing some of your applications.
Reason 7: When you don’t have a way to manage encryption keys
Encryption keys are easy to manage on physical servers. When secure workloads move around because of virtualization, encryption key management designed for physical servers won’t work. The obvious ways to solve to problem – using passwords or certificates stored on individual VMs – are not secure. Policy based encryption key management is a requirement if you’re going to run secure apps in
Reason 8: When you use clustered apps with built in failover
Modern virtualization platforms offer various flavors of high availability for VMs. Unfortunately, some applications, especially older, mission critical ones, also offer HA features. A good example is anything running Microsoft Cluster Services with a shared disk – setups like this will break in private clouds that allow VMs to automatically move around. If your virtualization platform is providing your HA, your apps shouldn’t, and vice versa.