Commentary

George Crump
 

Storage As A Virtual Machine Part Two - Details

As we dive deeper into the storage as a virtual machine concept we went back and re-interviewed some of the players in the storage as a virtual machine market, focusing specifically on what they provide. The first two conversations were with DataCore and HP. We will cover more suppliers as the series unfolds.

As we dive deeper into the storage as a virtual machine concept we went back and re-interviewed some of the players in the storage as a virtual machine market, focusing specifically on what they provide. The first two conversations were with DataCore and HP. We will cover more suppliers as the series unfolds.DataCore provides a virtual SAN appliance in a prepackaged download. It is important to note that this is not a special version of the software; their current storage virtualization software solutions can run as a virtual appliance unchanged. What they have done however is prepackaged the solution in a Virtual Hard Disk (VHD) format to simplify the loading of the software. This makes it simple for a storage manager to try out the product without having to acquire additional hardware. An example installation might be a two node virtual server environment. The VHD would be installed as a virtual machine on both. The available capacity on the two systems would then be cross mirrored between the two virtual machines. As additional traditional virtual machines are added they can be assigned storage from newly created virtual storage appliances.

Sharing is done via iSCSI across the network that connects to two physical hosts. Additional virtual hosts would have access to this shared storage by that iSCSI interconnection. Assuming there is excess capacity, this allows the virtual environment to quickly see how shared storage can benefit them without needing to purchase additional servers or storage. Most environments will move to a stand alone set of systems to serve up storage, although some work just fine in this configuration. Since there is no change to the software, migration from the virtual version to a standalone version it relatively straight forward.


More Storage Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

HP's LeftHand Networks is known for its clustered approach to storage, so bringing that concept to the virtual environment seems natural. Similar to DataCore, HP uses the same software in the virtual environment as it does in the stand alone environment, unlike the DataCore solution, the HP solution clusters storage across all the available server hosts in the virtual cluster. In this implementation a virtual machine is created on each physical host. Each virtual machine is assigned a specific amount of capacity, ideally the size of that capacity is consistent, and that capacity is then pooled into one logical partition. Then as regular virtual machines are created they are assigned capacity from that pool and data is striped across the virtual machines.

Similar to the DataCore example this is most often used to evaluate the LeftHand's storage software, but a growing number of users are using it as a production storage solution. HP also provides a product called Cluster Swap that can move the data from the virtual servers to a stand alone storage configuration.

While both of these solutions are most commonly deployed in evaluation scenarios, as the processing capabilities of the virtual hosts becomes more and more powerful there will be continued excess processing capacity. Why not use that capacity to manage the storage requirements of environments with modest storage I/O demands? With each iteration of the Intel processor, that performance capability will continue to increase and tempt more users to this type of solution.

Track us on Twitter: http://twitter.com/storageswiss

Subscribe to our RSS feed.

George Crump is lead analyst of Storage Switzerland, an IT analyst firm focused on the storage and virtualization segments. Find Storage Switzerland's disclosure statement here.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links