If you design your migration steps carefully, there will be no downtime. Unconfiguring the Stretch Cluster and changing the topology does not affect host I/O.
You need to carefully design this process: when you remove a copy of a volume or an I/O group from the Stretch Cluster, the hosts must still be able to access the surviving copy.
Original Message:
Sent: Tue June 02, 2026 01:52 AM
From: Bacil123
Subject: Enhanced Stretched Cluster
Thanks, Nezih. Much appreciated. so, out of the below steps, in which part there will be an outage/scheduled downtime. Unconfigure HyperSwap - Does this topo change will break something. Remove Enclosure - Does this means physical removal of the enclosure. Initialize a new system - which new system is this. Does this mean the process to start PBHA. Thanks.
Original Message:
Sent: Mon June 01, 2026 08:17 AM
From: Nezih Boyacioglu
Subject: Enhanced Stretched Cluster
Hi
There is an IBM Redbook about PB-HA which contains the migration method from Hyperswap to PB-HA. You can read it, but it does not cover the migration of Enhanced Stretch Clusters to PB-HA. However, the idea is almost the same and simple.
https://www.redbooks.ibm.com/abstracts/sg248569.html
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
------------------------------
Nezih Boyacioglu
IBM Community Hero
https://nezihboyacioglu.com
------------------------------