If you’re like a lot of people, a few years ago you probably began consolidating
your physical servers using a hypervisor. You then discovered that some of
your applications were running slowly, or that moving a virtual machine (VM)
from box to box was harder than you expected, requiring you to manually reestablish
the routing between the virtual app and its data stored somewhere
on the company SAN. In both cases, your hypervisor vendor likely told you that
your legacy storage was the root of the problem. To solve the problem once and
for all, your hypervisor maker said, you can abandon your old storage and jump
on board with something called hyper-converged storage.
Your first reaction might have been to ask, “How could it be legacy storage,
when I just deployed it?” The next question might have been “What the heck
is hyper-converged storage?” A search of the Web for more information on
hyper-converged storage probably turned up as many definitions for the term
as vendors offering products.
Analysts claim hyper-converged storage is actually a subset of hyper-converged infrastructure. The term hyper-converged infrastructure
typically refers to a cobbling together of server components with storage components
via some sort of software-defined storage (SDS) software “glue.” This
has usurped all those special features and functions that used to be operated
from array controllers and instead placed them into a software uber-controller
on the server side of the hyper-converged platform.
Download the whitepaper at: What is hyper-converged infrastructure?