(This post is the third in a series of posts around NetApp DataONTAP Cluster-Mode. You can read the first two posts here and here.)
In the last post, we talked a lot about a high-level overview of what Cluster-Mode brings to the table. To understand much further, we’re going to have to get our hands dirty and talk techie for a bit. Fear not, but this will be a little more techie than the others.
Let’s start with my own definition of a Vserver. This is not necessarily NetApp’s definition, but this is how I like to describe it to customers.
Datacenter Dude definition:
A Vserver is a memory-bound, cluster-wide, entity that fully abstracts all aspects of connecting backend storage from the physical array. Vservers act as a “front-end” to the array, and virtualize access by way of a per-protocol, per-node interface known as a LIF, or logical interface. Correlations can be drawn between Vservers and traditional virtual machines in the way that they take physical hardware and resources and abstract access to it, allowing for more efficient uses to be made of the physical investments.