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 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 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

Evelyn, another alternative could be:1. Break Hyperswap HA into SVCs (version 7.8).2. Virtualize the Flash5200 on the SVC.3. Create flash copy relationships between the SVC lun pool and the (virtualized) Flash pool.4. Once the luns have been copied, remove the FS from virtualization, and the host will now work with the luns already copied to the FS.

(I don't know if an SVC with v7.8 can virtualize an FS with v8.7)

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 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

I'm not sure why you would use flashcopy for this suggestion when vdisk mirroring wont' generate a new lun/uid.  and what you have proposed in your workflow doesn't leave you with an HA solution.

You can of course use image mode migration to move the data from the SVC to your new FlashSystem 5300 (which I suggested in my original set of options), you can do that without breaking the SVC HA, so you will lose HA as part of this.  I wouldn't recommend the workflow you have suggested for this migration, but it depends a lot on what you are trying to achieve, what your networking/host teams are willing to do, and how much transition/down time you are willing to take.

I hope this helps,

Evelyn, another alternative could be:1. Break Hyperswap HA into SVCs (version 7.8).2. Virtualize the Flash5200 on the SVC.3. Create flash copy relationships between the SVC lun pool and the (virtualized) Flash pool.4. Once the luns have been copied, remove the FS from virtualization, and the host will now work with the luns already copied to the FS.

(I don't know if an SVC with v7.8 can virtualize an FS with v8.7)

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 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

What happens is that my flash has version 8.7, and my SVC has version 7.8, so due to firmware issues they would not be compatible to leave them in HA, that is the reason why this plan is to migrate everything from the SVC by copying its LUNs to the FS5200 storage (virtualized in the SVC) and then once copied, remove the FS5200 from the SVC and run my hosts with it.

I'm not sure why you would use flashcopy for this suggestion when vdisk mirroring wont' generate a new lun/uid.  and what you have proposed in your workflow doesn't leave you with an HA solution.

You can of course use image mode migration to move the data from the SVC to your new FlashSystem 5300 (which I suggested in my original set of options), you can do that without breaking the SVC HA, so you will lose HA as part of this.  I wouldn't recommend the workflow you have suggested for this migration, but it depends a lot on what you are trying to achieve, what your networking/host teams are willing to do, and how much transition/down time you are willing to take.

I hope this helps,

Evelyn, another alternative could be:1. Break Hyperswap HA into SVCs (version 7.8).2. Virtualize the Flash5200 on the SVC.3. Create flash copy relationships between the SVC lun pool and the (virtualized) Flash pool.4. Once the luns have been copied, remove the FS from virtualization, and the host will now work with the luns already copied to the FS.

(I don't know if an SVC with v7.8 can virtualize an FS with v8.7)

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 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