Troubleshooting Metro Mirror sessions

Use this information to understand, isolate, and resolve problems with Metro Mirror sessions.

After you suspend a session, other sessions also become suspended
This condition occurs when you suspend a Metro Mirror session or Global Mirror session.
Metro Mirror session freezes when a hardware failure is detected
This condition occurs during normal operation.
All Metro Mirror sessions and copy sets are suspended
This condition occurs when the Copy Services Manager server lost connectivity to one of the storage systems, and the Metro Mirror sessions went to a suspended state. Then, when the management server regained connectivity, all of the Metro Mirror sessions and copy sets were suspended.
DS8000ESS/DS storage system suspends when the server stops sending a heartbeat to it
This condition occurs during normal operation.
Starting a session does not restart pairs outside the SAN Volume Controller or Storwize consistency group
This condition occurs when you issue a Start command for a Metro Mirror session or Global Mirror session with SAN Volume Controller or Storwize® storage systems.
Copy sets are in the prepared state but the session is suspended
This condition occurs during a Metro Mirror session.
IWNR2767W status message indicates one or more LSS pairings for an active role pair running in Metro Mirror mode has one logical path established
The condition can occur for any session running with DS8000® volumes and using Metro Mirror replication.