Changing the periodic source
You can change the periodic or asynchronous source only in the
3site_consistent
, 3site_inconsistent
, and stopped
states.
Changing the periodic or asynchronous source to a non-primary site is not supported if the remote copy relationship between the primary site and the auxiliary-near site is not active.
Both the management GUI and the command-line interface support excluding a near site; however, some status and objects are named differently between these interfaces. For example, in the management GUI, the site that completes replication to the auxiliary-far site is called the asynchronous source. In the CLI, the same concept is referred to as the periodic_source. In the management GUI, the overall status for 3-site consistency groups becomes Asynchronous only after a near site is excluded. In the CLI, the status of the 3-site consistency group becomes 2site_periodic.
Using the management GUI
- In the management GUI, select .
- 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
Note: Alternatively, on the 3-site partnership details page, select Switch asynchronous source from the selected 3-site consistency group overflow menu.
The Switch asynchronous source page appears and displays the current and new replication synchronous source type.
to change the flow of data to the auxiliary far site.
- On the Switch asynchronous source page, verify the switch to the new replication type and click Switch.
- When the process completes, go to the consistency group details page to verify the change in asynchronous source.
Using the command-line interface
To change the periodic source with the command-line interface, complete these steps:
- Run the ch3sitercconsistgrp -periodicsrc command to switch the periodic
source.
[root@ORCH-HOST cli]# ch3sitercconsistgrp -periodicsrc 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 periodic source
change.
[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 AuxNear consistent_synchronized stopped 350 online