To move volumes between I/O groups non-disruptively, ensure that hosts are mapped to the volume, support non-disruptive volume move. The cached data that is held within the system must first be written to the system disk before the allocation of the volume can be changed.
Modifying the I/O group that services the volume can be done concurrently with I/O operations if the host supports non- disruptive volume move. It also requires a rescan at the host level to ensure that the multipathing driver is notified that the allocation of the preferred node has changed and the ports by which the volume is accessed has changed. This can be done in the situation where one pair of nodes has become over used.
If there are any host mappings for the volume, the hosts must be members of the target I/O group or the migration fails.
Make sure you create paths to I/O groups on the host system. After the system has successfully added the new I/O group to the volume's access set and you have moved selected volumes to another I/O group, detect the new paths to the volumes on the host. The commands and actions on the host vary depending on the type of host and the connection method used. These steps must be completed on all hosts to which the selected volumes are currently mapped.
To move a volume between I/O groups using the CLI, complete the following steps: