Path specification for S-VOLs

Ops Center Administrator User Guide

Version
11.0.x
Audience
anonymous
Part Number
MK-99ADM001-21

Before Ops Center Administrator v11.0.3, you could set up individual paths for connecting each S-Vol in a remote replication group to the server. However, from v11.0.3 onwards, all S-VOLs in a remote replication group are assigned the same paths for connecting to the server.

For example, the following diagrams show the path created in legacy and remote replication groups when adding a new GAD pair (P-VOL#2, S-VOL#2) to an existing GAD pair (P-VOL#1, S-VOL#1):

Legacy remote replication groups

Paths are created to connect P-VOLs and S-VOLs to the selected ports in a one-to-one relationship:


Legacy remote replication group

Remote replication groups

For P-VOLs, path creation is similar to that of legacy remote replication groups. For S-VOLs, paths are created from each S-VOL in the remote replication group to all the ports that are being used by S-VOLs within the group.

This path configuration is a remote replication group specification. When changing the paths of P-VOLs and S-VOLs in the replication group, ensure they conform to this specification. Therefore, if you want to create separate connection paths, create an individual remote replication group for each GAD pair.

Note: When you edit the paths configuration for S-VOLs, paths are automatically created from each S-VOL in the remote replication group to all the ports that are being used by all S-VOLs within the group during the following operations:
  • Creating, attaching, and protecting volumes with high availability.
  • Protecting volumes with high availability.
  • Unprotecting volumes to remove GAD pair.

Remote replication group