Migrating a primary storage system to a newer DS8000 by using z/OS HyperSwap
You can migrate a primary storage system to a newer storage system in several ways, including the use of an external application. Use the information in this topic to migrate a primary storage system to a newer DS8000® by using DS8000 copy services and z/OS® HyperSwap® technology. You do not require a Copy Services Manager license as the migration can be done by using the preinstalled version of Copy Services Manager along with z/OS input/output supervisor (IOS) APAR OA62931.
Before you begin
- IOS APAR OA62931 must be installed on the z/OS system for HyperSwap migration support.
- If any volumes are attached to multiple sysplexes, the hardware reserves option must be
enabled.Note: Hardware reserve support is available for DS8000 9.1 and higher, contact support before enabling the option. For more information, see Managing hardware reserves.
About this task
The following steps are used to migrate a primary storage system to a newer DS8000 storage system. Migration works whether Copy Services Manager, DSCLI, or GDPS is managing the relationships.
This solution can be used to migrate volumes that are not replicated or volumes that are sources to Global Copy, Metro Mirror, and Global Mirror relationships. This solution is not supported for pairs that are in an existing multi-target relationship as it uses a multi-target relationship to replicate to the new storage system.
The solution uses z/OS HyperSwap technology to swap the primary storage system volumes to the new primary storage system volumes. The swapping is done without requiring customers to shut down their applications or the z/OS system or sysplex. A Copy Services Manager Migration session can now be setup to load a new type of HyperSwap configuration on z/OS, which disables swaps by event and allows the swap only by command. The primary storage system can be swapped to the new storage system with little to no application impact.
If the primary volumes are already in a remote copy relationship, a new Migration session is automatically generated in Copy Services Manager. After the swap completes, the new Migration session establishes a Global Copy relationship between the new primary volumes and the original secondary volumes without a full copy. You can assimilate these Global Copy relationships back into their existing Metro Mirror, Global Mirror, Copy Services Manager, or GDPS solution.