Recovering a Peer Persistence failover

If the Auto synchronize policy is not enabled and a Peer Persistence Remote Copy group fails over, you must recover the group manually using CLI commands. See the HPE Primera OS Command Line Interface reference guide for more information.

In this procedure, SystemA identifies the primary or source storage system in the original configuration. SystemB identifies the secondary or target storage system. During the failover, SystemA failed over to SystemB making SystemB the primary-rev storage system. SystemB replicates to SystemA.

Prerequisites

The DR state is Failover.
The reason for the failure is resolved.

Procedure

Log in to the secondary (failover) storage system.
Recover the target system.
```
cli% setrcopygroup recover -t <sync target>
```
Where: <sync target> is the name of the target on the primary system (SystemA).
The Remote Copy group on SystemA is changed from primary to secondary-rev.
Reverse the role of the Remote Copy groups.
```
cli% setrcopygroup reverse -natural -t <sync target>
```
The Remote Copy group on SystemA is changed from secondary-rev to secondary. The Remote Copy group on SystemB is changed from primary-rev to primary.
Wait for the volumes to synchronize.
```
cli% showrcopy
```
(Optional) To change the groups back to the original configuration:
```
cli% setrcopygroup switchover -t <sync target>
```
The Remote Copy group on SystemA is changed to primary. The Remote Copy group on SystemB is changed to secondary. The replication direction changes so that SystemA replicates to SystemB.