On June 10th, we announced IBM Hyper-Scale.
IBM® Hyper-Scale introduces two major new technologies, both implemented in the IBM XIV® Storage System (Gen3 models):
- The first is IBM Hyper-Scale Manager, a flexible, consolidated multi-system management application that was originally released in October 2012 as “Multi-System Manager”. IBM Hyper-Scale Manager is based on and seamlessly integrated with the XIV GUI and spans multiple XIV systems.
- The second new technology, IBM Hyper-Scale Mobility, is a powerful function for moving volumes between XIV Gen3 systems transparently, with no disruption to host applications.
IBM Hyper-Scale helps you easily overcome provisioning scenarios that normally challenge traditional systems. IBM Hyper-Scale can accommodate several critical customer scenarios for data mobility, load balancing, over-provisioning, and storage system repurposing.
The process of migrating volumes consist of just a few steps or stages:
Stage 1: Setup Create the volume on the destination XIV system and set up the relationships between the two volumes needed for migration.
Stage 2: Migration in progress Data migration can begin; New data is written by the host to the source and migrated (copied) to the destination. The source volume state goes from initializing to synchronized if the migration is successful. This is known as the Proxy_ready phase.
Stage 3: Proxying At this point, the administrator can instruct the source storage system to redirect host I/O to the new volume on the destination XIV. This stage corresponds to the Proxy phase.
In proxy mode, the source (now the proxy) no longer functions as a regular volume, and the source storage system communicates host requests to the destination. In proxy mode, the host can remain connected to the source; the host can be moved after the migrated volume data is on the destination.
Stage 4: Cleanup The final stage of the migration involves connecting the host directly to the new volume. This stage might require zoning changes, and the multi-path device driver must discover the new path to the migrated volume. Finally, the original paths can be removed and the IBM Hyper-Scale Mobility relationship can be deleted.
For details and step by step illustrations, refer to the IBM Redpaper 'IBM Hyper-Scale Mobility Overview and Usage", REDP-5007