content_image/1011850.jpg
Tip: Migrating volumes across I/O groups can be a disruptive action. Therefore, specify the correct I/O group at the time the volume is created. 

Also, when a volume is being created, it is possible to define a list of I/O groups in which a volume can be accessible to hosts. It is recommended that a volume is accessible to hosts only by the caching I/O group. You can have more than one I/O group in the access list of a volume in some scenarios with specific requirements, like when a volume is being migrated to another I/O group. 

GLYPH<SM590000> By default, the preferred node , which owns a volume within an I/O group, is selected for a load balancing  basis. Even though it is not easy to expect the workload when the volume is created, you should distribute the workload evenly on each node within an I/O group. 

GLYPH<SM590000> With the exception of a few cases, cache mode of a volume should be set to readwrite. More details can be found in section 5.12, “Volume cache mode” on page 135. 

GLYPH<SM590000> The maximum number of volumes per I/O group and system is described in Table 5-1. 

<img src='content_image/1011850.jpg'>

