Amazon, Azure and Google in race to the bottom … of cloud storage pricing

cw054-running-the-race-winning-the-prize

Good post by Chris Mellor (thank you) over at El Reg

Storage 2016 A period of quiet, rest and reflection is what the storage industry needs after a frankly hectic and very eventful 2015.

It won’t get it. The opposing forces of simplicity and complexity, access speed versus capacity, server versus array, on premises versus cloud, and tuned hardware and software versus software-defined are still in deep conflict. And don’t forget the containerisation issues in the background.

There is also a growing generalised attack on storage data access latency, just to add something else into the mix.

Read on here

VVOLs and VMware

Post by Christine Taylor (thank you)

The definition of VVOLs is simple but the effect is ground-breaking. Here is the simple definition part: Virtual Volumes (VVOL) is an out-of-band communication protocol between array-based storage services and vSphere 6.

And here is the ground-breaking part: VVOLs enables a VM to communicate its data management requirements directly to the storage array. The idea is to automate and optimize storage resources at the VM level instead of placing data services at the LUN (block storage) or the file share (NAS) level.

Read on here

Today’s Storage: Same As It Ever Was

Good post by Stephen Foskett (thank you)

Data storage has always been one of the most conservative areas of enterprise IT. There is little tolerance for risk, and rightly so: Storage is persistent, long-lived, and must be absolutely reliable. Lose a server or network switch and there is the potential for service disruption or transient data corruption, but lose a storage array (and thus the data on it) and there can be serious business consequences.

Read on here

VVOLs are more than just “per-VM”storage volumes

Good post by Luca Dell’Oca (thank you)

As I’m following closely the growth and evolution of this new technology for vSphere environments, and I’m still in search of a solution to play with VVOLs in my lab, I’ve found an article on the blogosphere and some additional comments on Twitter that made me re-think a bit about the real value of VVOLs.

It’s just a “per-VM” storage?

The original article comes from one of my favorite startups, Coho Data. In this article Suzy Visvanathan explains how Coho being an NFS-based storage doesn’t really need to support VVOLs.

Read on here

VAAI now available with vSphere Standard Edition

Post by Cormac Hogan (thank you)

A short post today, but it highlights what I feel is an important enhancement to vSphere licensing. I’ve had lots of questions recently about why VAAI (Storage APIs for Array Integration) is not available in the standard edition of vSphere.

Read on here

SDS – The Missing Link – Storage Automation for Application Service Catalogs

Post by Rawlinson Rivera (thank you)

Automation technologies are a fundamental dependency to all aspects of the Software-Defined Data center. The use of automation technologies not only increases the overall productivity of the software-defined data center, but it can also accelerate the adoption of today’s modern operating models.

In recent years, a subset of the core pillars of the software-defined data center has experienced a great deal of improvements with the help of automation. The same can’t be said about storage. The lack management flexibility and capable automation frameworks have kept the storage infrastructures from delivering operational value and efficiencies similar to the ones available with the compute and network pillars.

VMware’s software-defined storage technologies and its storage policy-based management framework (SPBM) deliver the missing piece of the puzzle for storage infrastructure in the software-defined data center.

Read on here

Virtual Volumes (VVols) and Replication/DR

Good post by Cormac Hogan (thank you)

There have been a number of queries around Virtual Volumes (VVols) and replication, especially since the release of KB article 2112039 which details all the interoperability aspects of VVols.

In Q1 of the KB, the question is asked “Which VMware Products are interoperable with Virtual Volumes (VVols)?” The response includes “VMware vSphere Replication 6.0.x”.

Read on here

Why Virtual Volumes?

Post by Andrew Sullivan (thank you)

How many times in the last 3-4 years have you heard “Virtual Volumes”, “VVols”, “Storage Policy Based Management”, or any of the other terms associated with VMware’s newest software-defined storage technology?  I first heard about VVols in 2011, when I was still a customer, and the concept of no longer managing my virtual machine datastores, but rather simply consuming storage as needed with features applied as requested, was fascinating and exciting to me.

Read on here

Virtual Volumes primer

Good post by Duncan Epping (thank you)

I was digging through my blog for a link to a virtual volumes primer article and I realized I never wrote one. I did an article which described what Virtual Volumes (VVol) is in 2012 but that is it. I am certain that Virtual Volumes is a feature that will be heavily used with vSphere 6.0 and beyond, so it was time to write a primer. What is Virtual Volumes about? What will they bring to the table?

Read on here

How do I get to the next level?

Very good post by Duncan Epping (thank you)

Every week I get an email from someone asking if I can mentor them, if I can help them get to the next level, if I can help them become a VCDX, if I can explain to them what I did to progress my career. I figured I would write an article for those who wonder what I did, this is not a magic formula by any means, following the same path and putting in the same amount of effort is no guarantee for success. There is also that thing called “being at the right place, at the right time” and of course seeing opportunities, grabbing opportunities and taking risks.

Read on here