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

Blogs

  • My Blogs
  • Public Blogs
  • My Updates
  • Administration
  • Log in to participate

▼ Tags

 

▼ Archive

  • November 2018
  • January 2018
  • November 2017
  • June 2017
  • May 2017
  • March 2017
  • February 2017
  • January 2017
  • December 2016
  • November 2016
  • October 2016
  • September 2016
  • August 2016
  • July 2016
  • May 2016
  • April 2016
  • March 2016
  • February 2016
  • January 2016
  • December 2015
  • November 2015
  • October 2015
  • September 2015
  • August 2015
  • July 2015
  • June 2015
  • April 2015
  • March 2015
  • February 2015
  • January 2015
  • December 2014
  • November 2014
  • October 2014
  • September 2014
  • August 2014
  • July 2014
  • June 2014
  • May 2014
  • April 2014
  • March 2014
  • February 2014
  • January 2014
  • December 2013
  • November 2013
  • October 2013
  • September 2013
  • August 2013
  • July 2013
  • June 2013
  • May 2013
  • April 2013
  • March 2013
  • February 2013

▼ Links

  • URL of site's RSS feed Storage Redbooks

▼ Blog Authors

IBM System Storage RedBooks

View All Entries
Clicking the button causes a full page refresh. The user could go to the "Entry list" region to view the new content.) Entry list

"Implementing VersaStack with Cisco ACI Multi-Pod and IBM HyperSwap for High Availability" IBM Redbooks

vasfi 1200008QSY | ‎ | 1,471 Views

The Redbooks team is pleased to announce the publication of  the follwing IBM Redbooks:

Implementing VersaStack with Cisco ACI Multi-Pod and IBM HyperSwap for High Availability 

 

The IBM Spectrum Virtualize HyperSwap function is a high availability feature that provides active-active access to a volume at two sites up to 300 km apart. HyperSwap functions are available on Spectrum Virtualize systems that can support more than one I/O group.

 

HyperSwap volumes maintain a fully independent copy of the volume data at each site. When data is written by hosts at either site, both copies are synchronously updated before the write operation is completed. If one site is no longer available, the other site continues to provide access to the volume. The following figure  shows an example Storwize HyperSwap configuration with underlying Volume Mirrors for additional redundancy.

image

 

 

In a HyperSwap configuration, each site is an independent failure domain. If one site experiences a failure, then the other site can continue to operate without disruption. You must
also configure a third site to host a quorum device or IP quorum application that provides an automatic tie-break during a link failure between the two main sites. The main site can be in
the same room or across rooms in the data center, buildings on the same campus, or buildings in different cities. Different kinds of sites protect against different types of failures.

 

In this book we discuss several IBM Spectrum Virtualize HyperSwap scenarios with VersaStack. The following shows the table of contents:

 

- Chapter 1 - Introduction and HyperSwap solution architecture
- Chapter 2 - Testing environment overview
- Chapter 3 -  Design and planning considerations
- Chapter 4 -  Implementing the HyperSwap solution
- Chapter 5 -  SVC HyperSwap diagnostic and recovery guideline


This book is intended for pre-sales and post-sales technical support professionals and storage administrators who are tasked with deploying a VersaStack solution with IBM HyperSwap.

 

I hope you enjoy the book!  If you have comments or questions, please use the Comments section of this blog below. Also, please let us know what topics you would like see in a future VersaStack/Storwize Redbooks.

 

Vasfi Gucer is an IBM Redbooks Project Leader. He works with technical experts to create books, guides, blogs, and videos.

 

image

image

 

 

Modified on by vasfi 1200008QSY
  • Add a Comment Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry
Notify Other People
notification

Send Email Notification

+

Quarantine this entry

deleteEntry
duplicateEntry

Mark as Duplicate

  • Previous Entry
  • Main
  • Next Entry
Feed for Blog Entries | Feed for Blog Comments | Feed for Comments for this Entry