• Share
  • ?
  • Profiles ▼
  • Communities ▼
  • Apps ▼

Blogs

  • My Blogs
  • Public Blogs
  • My Updates

LATEST TRENDS:

  • Log in to participate
Tony Pearson Tony Pearson is a Master Inventor and Senior IT Architect for the IBM Storage product line at the IBM Systems Client Experience Center in Tucson Arizona, and featured contributor to IBM's developerWorks. In 2016, Tony celebrates his 30th year anniversary with IBM Storage. He is author of the Inside System Storage series of books. This blog is for the open exchange of ideas relating to storage and storage networking hardware, software and services.
(Short URL for this blog: ibm.co/Pearson )
Facebook,   Twitter,   LinkedIn,   RSS Feed 

My books are available on Lulu.com! Order your copies today!

Featured Redbooks and Redpapers:

  • IBM System Storage Solutions Handbook
  • IBM Software-Defined Storage Guide
  • IBM Private, Public, and Hybrid Cloud Storage Solutions
  • IBM Spectrum Archive Enterprise Edition V1.2: Installation and Configuration Guide
  • IBM Spectrum Scale and ECM FileNet Content Manager Are a Winning Combination
  • IBM Spectrum Scale in an OpenStack Environment


IT featured blogger BlogWithIntegrity.com HootSuite Certified Professional

Links to other blogs...

  • Accelerate with ATS
  • Alltop - Top Storage Blogs
  • Anthony Vandewerdt
  • Barry Whyte (IBM)
  • Bob Sutor (IBM)
  • Brad Johns Consulting
  • Chris M. Evans
  • Chuck Hollis (Oracle)
  • Corporate Blogs
  • Greg Schulz
  • Hu Yoshida (HDS)
  • Jim Kelly (IBM)
  • Jon Toigo - DrunkenData
  • Kirby Wadsworth (F5)
  • Martin Glasborow
  • Raj Sharma, IBM Storage and Te...
  • Richard Swain (IBM)
  • Roger Leuthy, Storage CH Blog
  • Ron Riffe, "The Line"
  • Seb's SANblog
  • Stephen Foskett, Pack Rat
  • Steve Duplessie (ESG)
  • Storagezilla
  • Technology Blogs
  • Top 10 Storage Blogs
  • VMblog by David Marshall

Archive

  • April 2018
  • March 2018
  • February 2018
  • January 2018
  • December 2017
  • November 2017
  • October 2017
  • September 2017
  • August 2017
  • July 2017
  • May 2017
  • April 2017
  • March 2017
  • February 2017
  • January 2017
  • December 2016
  • November 2016
  • October 2016
  • September 2016
  • August 2016
  • May 2016
  • April 2016
  • February 2016
  • January 2016
  • December 2015
  • November 2015
  • October 2015
  • September 2015
  • May 2015
  • April 2015
  • March 2015
  • February 2015
  • January 2015
  • October 2014
  • September 2014
  • July 2014
  • June 2014
  • May 2014
  • April 2014
  • March 2014
  • February 2014
  • January 2014
  • December 2013
  • November 2013
  • October 2013
  • August 2013
  • July 2013
  • June 2013
  • May 2013
  • April 2013
  • March 2013
  • February 2013
  • January 2013
  • December 2012
  • November 2012
  • October 2012
  • September 2012
  • August 2012
  • July 2012
  • June 2012
  • May 2012
  • April 2012
  • March 2012
  • February 2012
  • January 2012
  • December 2011
  • November 2011
  • October 2011
  • September 2011
  • August 2011
  • July 2011
  • June 2011
  • May 2011
  • April 2011
  • March 2011
  • February 2011
  • January 2011
  • December 2010
  • November 2010
  • October 2010
  • September 2010
  • August 2010
  • July 2010
  • June 2010
  • May 2010
  • April 2010
  • March 2010
  • February 2010
  • January 2010
  • December 2009
  • November 2009
  • October 2009
  • September 2009
  • August 2009
  • July 2009
  • June 2009
  • May 2009
  • April 2009
  • March 2009
  • February 2009
  • January 2009
  • December 2008
  • November 2008
  • October 2008
  • September 2008
  • August 2008
  • July 2008
  • June 2008
  • May 2008
  • April 2008
  • March 2008
  • February 2008
  • January 2008
  • December 2007
  • November 2007
  • October 2007
  • September 2007
  • August 2007
  • July 2007
  • June 2007
  • May 2007
  • April 2007
  • March 2007
  • February 2007
  • January 2007
  • December 2006
  • November 2006
  • October 2006
  • September 2006

Disclaimer

"The postings on this site solely reflect the personal views of each author and do not necessarily represent the views, positions, strategies or opinions of IBM or IBM management."

(c) Copyright Tony Pearson and IBM Corporation. All postings are written by Tony Pearson unless noted otherwise.

Tony Pearson is employed by IBM. Mentions of IBM Products, solutions or services might be deemed as "paid endorsements" or "celebrity endorsements" by the US Federal Trade Commission.

This blog complies with the IBM Business Conduct Guidelines, IBM Social Computing Guidelines, and IBM Social Brand Governance. This blog is admistered by Tony Pearson and Sarochin Tollette.

Safe Harbor Statement: The information on IBM products is intended to outline IBM's general product direction and it should not be relied on in making a purchasing decision. The information on the new products is for informational purposes only and may not be incorporated into any contract. The information on IBM products is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. The development, release, and timing of any features or functionality described for IBM products remains at IBM's sole discretion.

Tony Pearson is a an active participant in local, regional, and industry-specific interests, and does not receive any special payments to mention them on this blog.

Tony Pearson receives part of the revenue proceeds from sales of books he has authored listed in the side panel.

Tony Pearson is not a medical doctor, and this blog does not reference any IBM product or service that is intended for use in the diagnosis, treatment, cure, prevention or monitoring of a disease or medical condition, unless otherwise specified on individual posts.

with Tags: heterogeneous Remove the tag from the selected filter tags - heterogeneous X
All posts
  • Sort by:
  • Date ▼
  • Title
  • Likes
  • Comments
  • Views

Storage Hypervisor integration with VMware

| | Visits (11278)

Over on the Tivoli Storage Blog, there is an exchange over the concept of a "Storage Hypervisor". This started with fellow IBMer Ron Riffe's blog post [Enabling Private IT for Storage Cloud -- Part I], with a promise to provide parts 2 and 3 in the next few weeks. Here's an excerpt:

"Storage resources are virtualized. Do you remember back when applications ran on machines that really were physical servers (all that “physical” stuff that kept everything in one place and slowed all your processes down)? Most folks are rapidly putting those days behind them.

In August, Gartner published a paper [Use Heterogeneous Storage Virtualization as a Bridge to the Cloud] that observed “Heterogeneous storage virtualization devices can consolidate a diverse storage infrastructure around a common access, management and provisioning point, and offer a bridge from traditional storage infrastructures to a private cloud storage environment” (there’s that “cloud” language). So, if I’m going to use a storage hypervisor as a first step toward cloud enabling my private storage environment, what differences should I expect? (good question, we get that one all the time!)

The basic idea behind hypervisors (server or storage) is that they allow you to gather up physical resources into a pool, and then consume virtual slices of that pool until it’s all gone (this is how you get the really high utilization). The kicker comes from being able to non-disruptively move those slices around. In the case of a storage hypervisor, you can move a slice (or virtual volume) from tier to tier, from vendor to vendor, and now, from site to site all while the applications are online and accessing the data. This opens up all kinds of use cases that have been described as “cloud”. One of the coolest is inter-site application migration.

A good storage hypervisor helps you be smart.

Application owners come to you for storage capacity because you’re responsible for the storage at your company. In the old days, if they requested 500GB of capacity, you allocated 500GB off of some tier-1 physical array – and there it sat. But then you discovered storage hypervisors! Now you tell that application owner he has 500GB of capacity… What he really has is a 500GB virtual volume that is thin provisioned, compressed, and backed by lower-tier disks. When he has a few data blocks that get really hot, the storage hypervisor dynamically moves just those blocks to higher tier storage like SSD’s. His virtual disk can be accessed anywhere across vendors, tiers and even datacenters. And in the background you have changed the vendor storage he is actually sitting on twice because you found a better supplier. But he doesn’t know any of this because he only sees the 500GB virtual volume you gave him. It’s 'in the cloud'."

Then another IBM blogger, Richard Vining, continued this meme with his post [VMware Data Protection with a Storage Hypervisor]. There are [different meanings for the word "protect"], but Richard's usage relates to protecting against unexpected loss. Here's an excerpt:

"Let’s start with a quick walk down memory lane. Do you remember what your data protection environment looked like before virtualization? There was a server with an operating system and an application… and that thing had a backup agent on it to capture backup copies and send them someplace (most likely over an IP network) for safe keeping. It worked, but it took a lot of time to deploy and maintain all the agents, a lot of bandwidth to transmit the data, and a lot of disk or tapes to store it all. The topic of data protection has modernized quite a bit since then.

Fast forward to today. Modernization has come from three different sources – the server hypervisor, the storage hypervisor and the unified recovery manager. The end result is a data protection environment that captures all the data it needs in one coordinated snapshot action, efficiently stores those snapshots, and provides for recovery of just about any slice of data you could want. It’s quite the beautiful thing."

At this point, you might scratch your head and ask "Does this Storage Hypervisor exist, or is this just a theoretical exercise?" The answer of course is "Yes, it does exist!" Just like VMware offers vSphere and vCenter, IBM offers block-level disk virtualization through the SAN Volume Controller(SVC) and Storwize V7000 products, with a full management support from Tivoli Storage Productivity Center Standard Edition.

SVC has supported every release of VMware since the 2.5 version. IBM is the leading reseller of VMware, so it makes sense for IBM and VMware development to collaborate and make sure all the products run smoothly together. SVC presents volumes that can be formatted for VMFS file system to hold your VMDK files, accessible via FCP protocol. IBM and VMware have some key synergies:

  • Management integration with Tivoli Storage Productivity Center and VMware vCenter plug-in
  • VAAI support: Hardware-assisted locking, hardware-assisted zeroing, and hardware-assisted copying. Some of the competitors, like EMC VPLEX, don't have this!
  • Space-efficient FlashCopy. Let's say you need 250 VM images, all running a particular level of Windows. A boot volume of 20GB each would consume 5000GB (5 TB) of capacity. Instead, create a Golden Master volume. Then, take 249 copies with space-efficient FlashCopy, which only consumes space for the modified portions of the new volumes. For each copy, make the necessary changes like unique hostname and IP address, changing only a few blocks of data each. The end result? 250 unique VM boot volumes in less than 25GB of space, a 200:1 reduction!
  • Support for VMware's Site Recovery Manager using SVC's Metro Mirror or Global Mirror features for remote-distance replication.
  • Data center federation. SVC allows you to seamlessly do vMotion from one datacenter to another using its "stretched cluster" capability. Basically, SVC makes a single image of the volume available to both locations, and stores two physical copies, one in each location. You can lose either datacenter and still have uninterrupted access to your data. VMware's HA or Fault Tolerance features can kick in, same as usual.

But unlike tools that work only with VMware, IBM's storage hypervisor works with a variety of server virtualization technologies, including Microsoft Hyper-V, Xen, OracleVM, Linux KVM, PowerVM, z/VM and PR/SM. This is important, as a recent poll on the Hot Aisle blog indicates that [44 percent run 2 or more server hypervisors]!

For a set of best practices combining VMware with SVC, check out this IBM Redpaper titled [VMware Proof of Practice and Performance Guidelines on the SAN Volume Controller].

Join the conversation! The virtual dialogue on this topic will continue in a [live group chat] this Friday, September 23, 2011 from 12 noon to 1pm EDT. Join me and about 20 other top storage bloggers, key industry analysts and IBM Storage subject matter experts to discuss storage hypervisors and get questions answered about improving your private storage environment.

technorati tags: IBM, Ron Riffe, Richard Vining, Storage Hypervisor, Cloud, Heterogeneous, Virtualization, SVC, Tivoli Storage, Productivity Center, TPC, VMware, vSphere, vCenter, ESX, Unified Recovery, Data Protection, EMC, VPLEX



Tags:  esx ron+riffe emc cloud vplex unified+recovery svc storage+hypervisor tivoli+storage heterogeneous ibm vsphere vmware tpc data+protection richard+vining vcenter productivity+center virtualization
  • Show:
  • 10
  • 20
  • 30
  • Previous
  • Next
1
Inside System Storage -- by Tony Pearson
  • Share
  • ?
  • Profiles ▼
  • Communities ▼
  • Apps ▼