Cloud Storage Solutions
We’ve recently released a new version of the Storage Enabler for Windows Failover Clustering. As you may know, it is a software agent that runs as a Microsoft Windows Server service on two geographically dispersed cluster nodes, providing failover automation for IBM XIV storage provisioning on these nodes, and enabling deployment of these nodes in a geo-cluster configuration.
The new version, 1.2.0, is mainly a maintenance release that resolves some previous limitations and provides support for the new IBM XIV and Microsoft Windows Server versions that have been released since version 1.1.0.
So, what's new in version 1.2.0? Here are the main things:
Support for Microsoft Windows 2012 R2
Support for XIV microcode versions 11.2, 11.3 and 11.4
Support for post-migrated Hyper-Scale Mobility volumes (supported in XIV microcode version 11.3 or later)
The IBM Hyper-Scale Mobility feature is used for online migration of volumes from one XIV storage system to another (for more detailed information, see "IBM XIV Storage System: IBM Hyper-Scale Mobility Overview and Usage" here: http://www.redbooks.ibm.com/abstracts/redp5007.html).
An important note to make is that previous IBM Storage Enabler versions (1.1.0 or earlier) could not be used to protect volumes that have been migrated through the Hyper-Scale Mobility feature. In such cases, you could no longer use the IBM Storage Enabler with these volumes.
Now, version 1.2.0 of the IBM Storage Enabler resolves this limitation by allowing protection after the final migration state (after performing ‘End Proxy’). Starting from this version, the IBM Storage Enabler can be reconfigured with the migrated volume and resume its protection in just a few steps.
Here is what you will need to do before the protection of the IBM Storage Enabler can be resumed on the migrated volume:
First, upgrade the IBM Storage Enabler on all the cluster nodes to version 1.2.0. Then, remove from the cluster any XIV volume that you want to migrate with Hyper-Scale Mobility. Once removed from the cluster, you can start the migration of these volumes.
When the migration process is complete, ensure that the original XIV proxy volume (which was migrated) is removed from the original XIV storage system. Also ensure that a mirror relationship between the source and XIV destination volumes exists.
You can then add the migrated XIV volumes back to the MSCS cluster.
Finally, run the following commands to add the XIV mirror resource dependency to the newly added (migrated) volumes, and to verify the configuration:
That’s it. As always, we are happy to receive any feedback!
The IBM Storage Host Software Group (HSG)
Hi everyone, we have some great news for VMware SRM 4.1.x users.
The new IBM XIV Adapter for VMware vCenter SRM 4.1.x was released!
The IBM XIV Adapter version 4.1.0 adds support for XIV's GEN3 systems, and also fixes a couple of bugs.
So if you are using SRM 4.1 - you can now use it with both XIV GEN2 (microcode version 10.2.x) and XIV GEN3 (microcode version 11.x)!
You can download the IBM XIV adapter software package from the SRM 4.1.2 download page (after clicking the View Downloads button, the IBM XIV adapter is listed on the page).
Feel free to ask us any question.
Lihi Tikolsky from the IBM XIV Host Software team.
ZivKalmanovich 2700044YXC 5,499 Views
It's raining new releases here at IBM HSG, the latest software released from our team is the IBM XIV HAK v2.1.0.
The HAK is already a well known, widely used toolkit, therefore in this post we will focus on what's new in this latest release, and what will you gain by installing or upgrading to this version.
The first feature to note is the added support for version 11.3.0 of XIV microcode and more importantly for the Online Volume Migration (OLVM) feature. Now the "good old" xiv_devlist utility also presents the OLVM state of each and every volume exposed to the server, providing the host and storage administrators an easily accessible tool to stay updated with the migration state of the volumes under their responsibility, without the need to access the XIV Management GUI.
In addition, the recently introduced host diagnostic utility, the XIV Host Profiler , can now be defined as a scheduled task right from the Host Attachment Kit Wizard - xiv_attach. No need to remember to set it separately, the user will be asked during host configuration if a task should be scheduled to run the utility periodically.
We've also improved the xiv_devlist and xiv_syslist commands' CSV file format output utilities. From this release, by adding the --no-headers argument, the column headers will be omitted from the generated CSV file.
On top of the above-mentioned features and enhancements several stability issues were also fixed. The detailed list of those issues can be found in the Release Notes document coupled with the software package.
To download the IBM XIV Host Attachment Kit v2.1.0 and the related documentation , please visit IBM Fix Central. You will need an IBM ID to download the files.
The IBM Host Software Group
We are pleased to let you know about our recently launched IBM Storage Host Software Solutions Information Center!
In this information center, or IC, you can find the relevant documentation of all the solutions that we offer, including information of both past versions and the latest versions.
Whether our host software solution is for XIV, DS8000, Storwize, or any other IBM storage system – the release notes, user guide, or installation guide are available on the IC in either PDF or HTML format (whatever suits you best).
The solutions are categorized on the navigation tree under four main categories: business continuity, management, host connectivity, and virtualization. Keep in mind, however, that some solutions could belong in more than one category. For example, a solution such as IBM Storage Management Console for VMware vCenter is placed under the virtualization category, but it may also be regarded as a powerful management solution. For another example, our XIV and SVC adapters for VMware vCenter Site Recovery Manager, also placed under virtualization, may also be regarded as business continuity solutions.
In any case, we hope that the organization of our solutions on the IC makes sense to you, and that the information is helpful. If not, please let us know! You can use the online feedback form that is available on the IC.
Each solution has its own welcome page from which you can have quick access to the information of the available versions. The PDF publications are available on the Publications page of each solution.
If you'd like to see our list of solutions per independent software vendor (ISV), check out the Solutions by ISV page. Alternatively, to see which solutions are available for a specific IBM storage system, check out the Solutions by storage system page.
And, of course, the IC is regularly being updated and improved. You can always check what's new on the IC by visiting the What's new page.
Lastly, we would like to thank our Information Development team for making it happen.
The HSG Team
Alon Marx 270006TGYS 5,280 Views
It's been a long 9 months since the release of the IBM XIV HAK 2.2.0 and we're back with a new exciting release - IBM XIV HAK 2.3.0 .
Example 1: Cleaning up a stale device
The next feature is also a response to customers needs. People using Veritas Dynamic Multi-Pathing (DMP) had issues running xiv_attach, as it always configured and initiated the native multipath framework. Two multipath frameworks on the same host is like having two managers not speaking to each other, each pulling in another direction.
Example 2: xiv_attach in presence of Veritas DMP
A third feature relates to the new release of XIV Microcode 11.5 and a feature we call Multi-Tenancy. Let's say you have two companies working on the same storage, each with it's own data that should never ever get to the other company. The storage can be divided into domains so that each is maintained by separate people, unaware of each others work. From the point of view of the storage administrator running xiv_attach or xiv_iscsi/fc_admin, he just uses his credentials to connect to the storage and everything behaves as expected. In case a user is able to see more than one domain (e.g. in case of domain per department) he is able to specify the domain the host should be using via a flag in the xiv_iscsi/fc_admin command line.
ZivKalmanovich 2700044YXC 5,233 Views
We have just made the latest version of IBM Storage Enabler for Windows Fail-over Clustering publicly available on IBM Fix Central.
I would like to highlight some of the new features and improvements introduced in version 1.1.0:
In addition several major issues were resolved, such as those related to deployments where XIV disks resided in the 'Available Storage' cluster group and issues related to XIV Mirror resource behavior upon Cluster Service failure.
The new version of the IBM Storage Enabler for Windows Fail-over Clustering and the related documentation can be found here.
Happy Clustering !
The IBM Host Software Group
VMware administrator, provision new datastores for your applications yourself, using IBM Storage Enhancements for vSphere Web Client. Use abstracted storage services, provided by your storage administrator. The services are consistent with application requirements with extendable storage space and VVol support. IBM Storage Enhancements for vSphere Web Client come packaged with IBM Spectrum Control Base Edition, a nifty storage provisioning tool integrated with a variety of VMware solutions for automation, monitoring, orchestration and native support of VVols and VASA API. Check the solution overview on YouTube at https://youtu.be/tf-0LGABZK8.
To make this happen, IBM has teamed up with VMware, creating a better experience for administrators and end users. We are proud to be one of the first partners in VMware's Web Client Plug-in certification program.
We are glad to announce the release of Spectrum Control Base Edition (SCBE) 3.1.
This new version introduces the following improvements:
Spectrum Control Base Edition 3.1 can be downloaded from Fix Central:
We'd be glad to hear your feedback!
We are proud to announce that the IBM Storage Driver for OpenStack has been recently upgraded to a new version - 1.6.0. This version brings support for OpenStack Liberty release, as well as for DS8870 microcode version 7.5 SP3 and DS8880 version 8.01. In addition, this release introduces the XIV and Spectrum Accelerate support for the OpenStack consistency groups. It also brings in the RESTful API that replaced the Java-based ESSNI driver in DS8000 storage systems.
We are happy to announce the release of an updated OpenStack Cinder driver for IBM Spectrum Virtualize, Storwize Family and FlashSystem V9000. This release complies with OpenStack Liberty specifications, emphasizing IBM's continuous commitment to making the cutting-edge OpenStack features available for IBM storage customers.
Another change is the enabling or disabling the fast format option during thick volume creation. As some volume operations are disabled until fast format is completed, the customer can now skip the fast format, when creating a thick volume. This makes the volume operational immediately after its creation.
Version 7.6 of IBM Spectrum Virtualize and Storwize Family will be supported after its release with no additional Cinder driver code change.