Zoning considerations for Remote Copy Switches

This topic provides information about the switch zoning considerations to support the Remote Copy service.

SAN configurations that use the Remote Copy feature between two clusters need additional switch zoning considerations. These considerations include:

Note:Note: These considerations do not apply if the simpler, intracluster mode of Remote Copy operation is in use, when only a single cluster is needed.

For intracluster Remote Copy relationships, no additional switch zones are required. For intercluster Remote Copy relationships, you must:

  1. Form a SAN that contains both clusters that are to be used in the Remote Copy relationships. If cluster A is in SAN A originally, and cluster B is in SAN B originally, this means that there must be at least one fibre-channel connection between SAN A and SAN B. This connection will be one or more inter-switch links. The fibre-channel switch ports associated with these inter-switch ports should not appear in any zone.
  2. A single SAN can only be formed out of combining SAN A an SAN B if the domain numbers of the switches in each SAN are different, prior to the connection of the two SANs. You should ensure that each switch has a different domain ID before connecting the two SANs.
  3. Once the switches in SAN A and SAN B are connected, they should be configured to operate as a single group of switches. Each cluster should retain the same set of zones that were required to operate in the original single SAN configuration.
  4. A new zone must be added that contains all the switch ports that are connected to SAN Volume Controller ports. This will contain switch ports that were originally in SAN A and in SAN B.
  5. You can adjust the switch zoning so that the hosts that were originally in SAN A can see cluster B. This allows a host to examine data in both the local and remote cluster if required. This view of both clusters is purely optional and in some cases may complicate the way you operate the overall system, therefore, unless specifically needed, it should not be implemented.
  6. You should verify that the switch zoning is such that cluster A cannot see any of the back-end storage owned by cluster B. Two clusters may not share the same back-end storage devices.

The following zones would therefore be needed in a typical intercluster Remote Copy configuration:

  1. A zone in the local cluster that contains all the ports in the SAN Volume Controller nodes in that local cluster and the ports on the backend storage associated with that local cluster. These zones would be required whether or not Remote Copy were in use.
  2. A zone in the remote cluster that contains all the ports in the SAN Volume Controller nodes in that remote cluster and the ports on the back-end storage associated with that remote cluster. These zones would be required whether or not Remote Copy were in use.
  3. A zone that contains all the ports in the SAN Volume Controller nodes in both the local and remote cluster. This zone is required for intercluster communication and is specifically required by Remote Copy.
  4. Additional zones that contain ports in host HBAs and selected ports on the SAN Volume Controller nodes in a particular cluster. These are the zones that allow a host to see VDisks presented by an I/O group in a particular cluster. These zones would be required whether or not Remote Copy were in use.
Notes:
Notes:
  1. While it is normal to zone a server connection so that it is only visible to the local or remote cluster, it is also possible to zone the server so that the host HBA can see nodes in both the local and remote cluster at the same time.
  2. Intracluster Remote Copy operation does not require any additional zones, over and above those needed to run the cluster itself.

(C) Copyright International Business Machines Corporation 2003, 2004