Changing the primary site

Edit online

Verify that the current primary site is in the stopped state before you change the primary site in a 3-site consistency group.

Consider the following information for management GUI-based operations:

You cannot change the primary site on a system that uses HyperSwap® topology.
The consistency group states must be in consistent, inconsistent, and stopped states when the Metro Mirror relationship between the primary site and the auxiliary-near site is operational.
Ensure that before you switch primary sites, all hosts and applications that access data on the original primary site must be relocated to the new primary site to ensure access to data is not lost.

Using the management GUI

To change the primary site of replication to another site in a 3-site consistency group by using the management GUI, complete the following steps:

In the management GUI, select Copy Services > Remote Copy.
Under Partnerships, select 3-site partnership.
On the details page for the 3-site partnership, select a 3-site consistency group to open the details page for the group.
On the consistency group details page, select Actions > Switch primary to change the primary source of replication to another site.
Note: Alternatively, on the 3-site partnership details page, select Switch primary from the selected 3-site consistency group overflow menu.

The Switch primary page displays the current and new primary sites.
On the Switch primary page, verify the switch to the new primary site and click Switch.
When the process completes, go to the consistency group details page to verify the changes.

Using the command-line interface

Consider the following information:

You cannot change the primary site on a system that uses HyperSwap topology.
For command-line operation, follow this procedure in the 3site_consistent, 3site_inconsistent, and stopped states when the Metro Mirror relationship between the primary site and the auxiliary-near site is operational. As a result, the sync_copy_state value is consistent_synchronized.
The application must be in the stopped state on the current primary site.

Run the ls3sitercconsistgrp command.

[root@ORCH-HOST cli]# ls3sitercconsistgrp
name state            primary periodic_copy_source sync_copy_state         periodic_copy_state freeze_time cycle_period status
CG0  3site_consistent Master  Master              consistent_synchronized  stopped                         350          online

Run the ch3sitercconsistgrp -primary command to change the primary site.
In the example, the command changes the primary site of the consistency group CG0.
```
[root@ORCH-HOST cli]#  ch3sitercconsistgrp -primary AuxNear CG0
```
The 050988 Configuration change requested by the last command has completed successfully event notification confirms that the procedure is successful. The event is generated on the clustered system at the auxiliary-far site. If the auxiliary-far site is down, the event is generated on the master clustered system. The 050990 Configuration change requested by the last command has failed event notification indicates that the procedure failed. Confirmation of the result of the command can be found in the event log. For more information, see Informational events.

Run the ls3sitercconsistgrp command to verify the primary site.

[root@ORCH-HOST cli]# ls3sitercconsistgrp
name state            primary periodic_copy_source sync_copy_state         periodic_copy_state freeze_time cycle_period status
CG0  3site_consistent AuxNear Master              consistent_synchronized  stopped                         350          online