MENU
The Need For Liquidity in Data Storage Infrastructure
Posted by Jon Toigo on August 17, 2017
No ratings yet.

Liquidity is a term you are more likely to hear on a financial news channel than at a technology trade show.  As an investment-related term, liquidity refers the amount of capital available to banks and businesses and to how readily it can be used.  Assets that can be converted quickly to cash (preferably with minimal loss in value) in order to meet immediate and short term obligations are considered “liquid.”

When it comes to data storage, liquid storage assets can be viewed as those that can be allocated to virtually any workload at any time without compromising performance, cost-efficiency/manageability, resiliency, or scalability.  High liquidity storage supports any workload operating under any OS, hypervisor, or container technology, accessed via any protocol (network file systems, object storage, block network, etc.), without sacrificing data protection, capacity scaling, or performance optimization.

Hard disk drive cost per gigabyte

(more…)

Please rate this

Design a ROBO infrastructure. Part 4: HCI solutions
Posted by Andrea Mauro on June 7, 2017
5/5 (1)

2-nodes hyperconverged solution

As written in the previous post, for ROBO scenario the most interesting HCI (Hyper-Converged Infrastructure) configuration is a two nodes configuration, considering that two nodes could be enough to run dozen VMs (or also more).

For this reason, not all hyperconverged solutions could be suitable for this case (for example Nutanix or Simplivity need at least 3 nodes). And is not simple scale down an enterprise solution to a small size, due to the architecture constraints.

Actually, there are some interesting products specific for HCI in ROBO scenario:

  • VMware Virtual SAN in a 2 nodes clusters
  • StarWind Virtual Storage Appliance
  • StorMagic SvSAN

StarWind Virtual SAN overall architecture

(more…)

Please rate this

Design a ROBO infrastructure (Part 3): Infrastructure at remote office side
Posted by Andrea Mauro on March 30, 2017
No ratings yet.

Design a ROBO scenario must match finally the reality of the customers’ needs, its constraints but also the type of workload and the possible availability solutions of them.

Logical design of a ROBO scenario

When can found the different type of approaches:

  • No server(s) at
  • Few servers (that maybe can fail)
  • Some servers with “relaxed” availability requirements
  • Some servers with reasonable availability

Let’s analyze each of them.

Design a ROBO scenario must match finally the reality of the customers’ needs, its constraints but also the type of workload and the possible availability solutions of them.

Hyper-Converged Infrastructure structure

(more…)

Please rate this

HYPER-CONVERGENCE TAKES HOLD
Posted by Jon Toigo on February 18, 2016
4.38/5 (8)

Hyper-converged infrastructure, when we started to hear about it last year, was simply an “appliantization” of the architecture and technology of software-defined storage (SDS) technology running in concert with server virtualization technology. Appliantization means that the gear peddler was doing the heavy lift of pre-integrating server and storage hardware with hypervisor and SDS hardware so that the resulting kit would be pretty much plug-and-play.

HCI

(more…)

Please rate this