Using active and standby Copy Services Manager servers with HyperSwap

You can set up an active and standby management server configuration with HyperSwap.

Active and standby servers with z/OS HyperSwap

When the storage system is set up to connect through the z/OS interface, the connection information is sent to the standby server and a connection is attempted. The connection might fail if the standby server does not run on a z/OS operating system or does not have access to the same volumes. If the connection fails and the standby server resumes the processing, the standby server cannot manage the HyperSwap processing.

On the z/OS system, if the session configuration was successfully loaded before the HyperSwap processing, the z/OS system can manage the HyperSwap processing. If the z/OS system swaps the volumes but cannot communicate with the Copy Services Manager server, the session is set to Suspended or Severe state. To set the session to Target Available state, clear the Manage H1-H2 with Hyperswap option, and issue the Recover command for the session.

Active and standby servers with AIX HyperSwap

When there is an active and standby management server configuration and a host system connection is added to the active server, a connection is attempted between the host system and the standby server. After AIX loads the session configuration, HyperSwap processing is possible only if there is communication between AIX and the Copy Services Manager server. If a standby server resumes the processing and is unable to connect to the host system that manages the swap, the session cannot run HyperSwap processing. You must activate communication to the host system before the session can run HyperSwap processing.