By Zenith Infotech 1

Recently, I finally saw an episode of the much-talked-about TV series “Catfish,” in which people in online-only relationships finally meet the other person, (usually) discovering that the online persona and the real person are very different. The episode reminded me of a blog my coworker wrote earlier this year about the difference between virtual and physical systems.

Understanding the performance demands of virtual infrastructures is vital when designing the physical systems that run them. As we turn to virtualization and the Cloud, we must integrate physical devices to support virtual systems. We’ve gone from a one server–one application world to one in which many systems all access the same storage.

The performance of traditional SANs in virtual infrastructures is often inadequate, and the difference between locally attached and virtually provisioned storage can be very noticeable. Why is that? What aspects of traditional SANs are in conflict with virtual infrastructures? Below, I share my colleague’s thoughts on the importance of “VM awareness,” or the ground-up design of a SAN to support virtualization demands.

Physical vs Virtual System Performance

A traditional iSCSI SAN uses LUNs as the basic management abstraction. This presents problems when they are integrated with a virtual architecture, which is managed using VMs and virtual disks. The volumes are configured and managed independently of the virtual infrastructure, requiring administrators to manage mapping and create VM policies to effectively manage the storage.

In addition to the management complexity, traditional SANs also suffer from latency and random disk-read issues. Most SANs are designed to handle predictable input and output patterns from one system. Predictive “pre-fetching” algorithms anticipate upcoming operations to improve performance and reduce wait times.

With virtual architectures, this pattern is turned on its head. Now, multiple servers and machines are all accessing the storage at the same time in a random pattern, often called the I/O Blender. This can easily overwhelm the system, and cause performance bottlenecks that make the system lag or freeze.

Bridging the Physical and Virtual

A SAN needs to integrate several features in order to effectively accommodate a virtual environment.

Merging the Physical and Virtual

It is vital that you understand how virtual infrastructures differ from physical ones, and be sure that the technology you use is designed with this in mind. If “Catfish” teaches us anything, it’s that you need to validate in order to ensure compatibility.

John McCallum is VP of Sales at Zenith Infotech. Zenith Infotech specializes in delivering enterprise-class IT solutions for virtualization, storage, and backup & recovery.  Zenith partners with IT providers serving the SMB market so they can capitalize on the lucrative cloud market. Learn more at www.zenithinfotech.com or email [email protected].