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)