storage:svc_hyperswap_migrate
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
storage:svc_hyperswap_migrate [2023/03/14 23:09] manu |
storage:svc_hyperswap_migrate [2025/03/31 18:52] (current) manu |
||
|---|---|---|---|
| Line 2: | Line 2: | ||
| https://www.ibm.com/docs/en/flashsystem-5x00/8.4.x?topic=details-hyperswap-system-configuration | https://www.ibm.com/docs/en/flashsystem-5x00/8.4.x?topic=details-hyperswap-system-configuration | ||
| + | |||
| + | NEW on v8.7.0.X **multi-IOgroup is disabled** !!! You have to enable it first ==> System ==> Gui preferences | ||
| + | |||
| + | Layer has to be in mode replication | ||
| + | <cli prompt='>'> | ||
| + | > chsystem -layer replication | ||
| + | </cli> | ||
| First set site for all components: | First set site for all components: | ||
| Line 16: | Line 23: | ||
| * Once the migration of data and hosts is done, and the second system is prepared to be added to the first, you need to run **leavecluster -force** on both it's nodes, which will make them candidate. | * Once the migration of data and hosts is done, and the second system is prepared to be added to the first, you need to run **leavecluster -force** on both it's nodes, which will make them candidate. | ||
| - | <cli> | + | <cli prompt='>'> |
| - | chsystem -topology hyperswap | + | > chsystem -topology hyperswap |
| </cli> | </cli> | ||
| Line 24: | Line 31: | ||
| * When the above is agreed and the HyperSwap is established, you can start making the existing volumes HyperSwap volumes, which is done via the link I sent in my initial post -> Right click on the vdisk -> Add Vdisk copy and then follow the procedure in the GUI. | * When the above is agreed and the HyperSwap is established, you can start making the existing volumes HyperSwap volumes, which is done via the link I sent in my initial post -> Right click on the vdisk -> Add Vdisk copy and then follow the procedure in the GUI. | ||
| * Once this is done and the data is migrated, you will have a fully fledged HyperSwap cluster. Also make sure that all volumes are hyperswapped, as otherwise, the purpose of this topology is a bit lost. Hosts need to have access to both "sites" and equal paths to both I/O groups, in order to operate properly, in case one of the systems undergoes maintenance or encounters an issue. | * Once this is done and the data is migrated, you will have a fully fledged HyperSwap cluster. Also make sure that all volumes are hyperswapped, as otherwise, the purpose of this topology is a bit lost. Hosts need to have access to both "sites" and equal paths to both I/O groups, in order to operate properly, in case one of the systems undergoes maintenance or encounters an issue. | ||
| + | |||
| + | Change synchronization speed | ||
| + | <cli prompt='>'> | ||
| + | > chpartnership -linkbandwidthmbits 2048 -backgroundcopyrate 50 mysystem | ||
| + | </cli> | ||
| + | |||
| + | Change synchronization speed | ||
| + | <cli prompt='>'> | ||
| + | > chsystem -relationship_bandwidth_limit 300 | ||
| + | </cli> | ||
| + | |||
| + | **relationship_bandwidth_limit**\\ | ||
| + | Indicates the current relationship bandwidth limit setting. The relationship bandwidth limit controls the maximum rate at which any one remote-copy relationship can synchronize. The default value for the relationship bandwidth limit is 25 megabytes per second (MBps). | ||
| + | |||
| + | == To convert a standard volume to an hyperswap volume == | ||
| + | |||
| + | You can use the management GUI or the command-line interface to convert a basic volume to a HyperSwap® volume. You convert the basic volume by adding another copy of the volume in a second site. | ||
storage/svc_hyperswap_migrate.1678831792.txt.gz · Last modified: 2023/03/14 23:09 by manu
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: GNU Free Documentation License 1.3
