Global Storage

I have to migrate an existing cluster HypwerSwap (SVCs) to a new cluster HyperSwap (FlashSystem5300), 

I have doubts about what would be the best method to carry out the migration

Hello!

First off, please make sure you are aware that Hyperswap is a legacy technology that is not supported past software release 8.7.0. (Please see https://www.ibm.com/support/pages/node/7166967).

If you are deploying a new system, I would recommend starting the design with Policy Based HA as the management, scalability and performance are much improved when compared to hyperswap.

Having said the above - If you are in an HA on your SVC and you are moving to FlashSystem 5300 you will need to either:
1: Use host based migration tools
2: break the HA and migrate to the 5300 (there are a number of ways to do this) than recreate the HA
3: Use image mode migration from the primary/master site - This will require you to take a host IO outtage when you switch from the SVC to the 5300 based volume.  Additionally I believe (I'm not certain) that you will not be able to have HA on the 5300 during this time, and will lose it at the point you migrate and have to re-establish it.  This is probably the more complex path with some challenges in the configuration.  

I have doubts about what would be the best method to carry out the migration

Thank you so much Evelyn.

I have revewed the documentacion and i found this :

6.3 Migrating from HyperSwap to policy-based HA :

One significant difference when you migrate from HyperSwap to policy-based HA is that with
HyperSwap, two storage enclosures are clustered together as a two-IO-group system and are
acting as a single managed entity. For policy-based HA, the two storage enclosures are
individual enclosures not clustered together. High availability is managed through hosts and
volumes in storage partitions that span two individual storage enclosures

The following steps are involved in converting a two-storage-enclosure HyperSwap
configuration to a policy-based HA setup:
1. Unmirror HA-volumes
Convert all HyperSwap volumes to basic volumes and leave a volume copy on only the
remaining enclosure (IO-group).
2. Migrate non-HA-volumes
Migrate all non-HA volumes to the remaining enclosure (IO-group).
3. Unconfigure HyperSwap
Change topology to standard.
4. Remove enclosure
If IO-group 0 is the remaining enclosure, then remove the nodes from I/O group 1. The
nodes in IO-group 1 change to state Candidate.
5. Initialize a new system
Create a new system by using the nodes from I/O group 1.
6. Configure policy-based HA
When you have two independent storage systems defined, you can configure policy-based
HA between them

Important: There is currently no method to migrate from HyperSwap to policy-based HA
while maintaining high availability during migration.

Very similar to what you write me.

I have doubts about what would be the best method to carry out the migration