Restoring the replication configuration and access to data after a system recovery (T3 recovery)

Edit online

Contact IBM® Support Center for assistance with restoring the configuration, access to data, replication partnerships, and relationships. Replication partnerships and relationships are not automatically restored following a system recovery.

Consider the following information about a T3 disaster at a non-primary near site:
- A cascade configuration changes to the stopped state. Then, you can change the periodic source and continue data cycling in a star configuration until the secondary site is recovered.
- A star configuration changes to the 2site_periodic state. You can continue data cycling until the secondary site is recovered.

Consider the following information about a T3 disaster at a primary near site:

All 3-site consistency groups are in the stopped state. Until the primary site is recovered, two options are available:

Option 1 is to not run any application I/O on the surviving site and the consistency groups remain in the stopped state.

rc_cg11 stopped BR_SITE PR_SITE consistent_disconnected stopped 2019/06/22/20/06/55 300 primary_offline                 
 rc_cg13 stopped BR_SITE BR_SITE consistent_disconnected stopped 019/06/22/20/09/20  300 primary_and_periodic_src_offline
 rc_cg15 stopped BR_SITE BR_SITE consistent_disconnected stopped 2019/06/22/20/09/45 300 primary_and_periodic_src_offline

Option 2 is to run application I/O on the surviving site and enter the stoprcconsistgrp -access command to stop the 2-site consistency group.
If the consistency group is in a cascade topology, the consistency group enters the 2site_periodic state. For the remaining consistency groups, change the periodic source to run in the 2site_periodic state.
```
 rc_cg11 2site_periodic PR_SITE idling_disconnected stopped 2019/06/22/20/20/25 300 primary_offline
 rc_cg13 2site_periodic PR_SITE idling_disconnected idling 2019/06/22/20/09/20 300 primary_offline
 rc_cg15 2site_periodic PR_SITE idling_disconnected idling 2019/06/22/20/09/45 300 primary_offline
```