Recovery actions that require assistance from IBM Support

Edit online

In a 3-site configuration that uses a HyperSwap® topology, certain recovery use cases have potential for data loss if completed incorrectly.

CAUTION:
Do not attempt the following recovery use cases without assistance from IBM® Support. Data loss can result if data access and replication is not restored correctly.
Recovering data access and replication after system recovery (T3 recovery) on an auxiliary-far site system
Data access to a HyperSwap system is not disrupted when the system on the auxiliary-far site completes system recovery. However, 3-site data access and replication are affected.
To recover data access, complete the following steps:
  1. On the orchestrator host, enter the following command: 
    stop3sitercconsistgrp name

    Where name is the name of the 3-site consistency group for the HyperSwap configuration.

  2. Verify that the state of the consistency group changes to stopped.
  3. Use the system recovery (T3 recovery) procedures on the system at the auxiliary-far site. For more information, see Recover system procedure.

  4. Contact IBM Support to restore data access, configuration, and replication objects, including partnerships and relationships at the auxiliary-far site.

Recovering data access and replication after system recovery (T3 recovery) on a HyperSwap system
Data access to a HyperSwap system is disrupted when a HyperSwap system on both near sites completes system recovery. Before you complete system recovery, complete the following steps:

Contact IBM Support before you follow this procedure.

  1. Enter the following command to verify that when the condition occurs, the 3-site consistency groups are in the stopped state:
    ls3sitercconsistgrp
  2. On the orchestrator host, enter the convertrcconsistgrp command to make the auxiliary-far site volumes accessible and convert the 3-site consistency group to a 2-site consistency group.
    convertrcconsistgrp -type 2site name
  3. Contact IBM Support Center to recover the HyperSwap system and the 3-site configuration. For more information, see Recover system procedure.
Recovering from a loss of an I/O group on any near site in a HyperSwap system with the status partner_dead_domain
In this case, the entire I/O group for the HyperSwap system is not accessible. Although data access to the HyperSwap system is not disrupted, replication must be restored.

For more information about this error, go to Messages and codes > Error codes > 1895.

To verify the loss of the I/O group, complete the following steps:
  1. Enter the following command on the orchestrator host: 
    ls3sitercconsistgrp name

    Where name is the name of the 3-site consistency group for the HyperSwap configuration.

  2. Verify that the state of the consistency group changes from 3site_consistent to 2site_periodic. In addition, the status of the consistency group changes to partner_dead_domain.
  3. Contact IBM Support to recover the I/O group of the HyperSwap system and to restore 3-site replication.
Recovering from a loss of an I/O group on an auxiliary-far site
Data access to the HyperSwap system is not disrupted when the I/O group is not accessible on the system at the auxiliary-far site. The HyperSwap system continues to handle incoming host I/O; however, 3-site replication is impacted.

For more information about this error, go to Messages and codes > Error codes > 1895.

To verify the loss of the I/O group, complete the following steps:
  1. Enter the following command on the orchestrator host:
    ls3sitercconsistgrp name

    Where name is the name of the 3-site consistency group for the HyperSwap configuration.

  2. Verify that the state of the 3-site consistency group changes to stopped.
  3. Contact IBM Support to recover the I/O group of the system on the auxiliary-far site and to restore 3-site replication.
Recovering from near-site-dual disasters

Contact IBM Support before you use this procedure to recover from near-site-dual disasters. Before you attempt to recover from dual disasters at any other two sites, contact IBM Support.

  1. Verify that when the condition occurs, the 3-site consistency groups are in the stopped state.

    Verify that the 050993 3-site consistency group is now in STOPPED State event notification is received. View the event notification in the event log. For more information, see Informational events.

  2. Enter the convertrcconsistgrp command to make all the auxiliary-far site volumes accessible and convert the 3-site consistency group to a 2-site consistency group.
  3. Contact IBM Support Center to recover the HyperSwap system and the 3-site configuration.