Global Mirror commands

Edit online

Use this information to learn about commands available for Global Mirror sessions. To issue a command, go to Session Actions > Commands and click the command.

Table 1. Global Mirror commands
Command	Action
Enable Copy to Site 1	Run this command and confirm that you want to reverse the direction of replication before you reverse the direction of copying in a failover and failback session. After you issue this command, the Start H2->H1 command becomes available.
Enable Copy to Site 2	Run this command and confirm that you want to reverse the direction of replication before you reverse the direction of copying in a failover and failback session. After you issue this command, the Start H1->H2 command becomes available.
Recover	Issue this command to recover the session to the target site. This command performs the steps necessary to make the target host volumes consistent and available for access as the new primary site. After this command completes, the session state becomes Target Available. Do not access H2 volumes until the Recover command is completed and the session displays Target Available and Recoverable. A Recover to H2 also establishes a point-in-time copy to J2 to preserve the last consistent data.
Refresh States	Refreshes the states of the role pairs that are in the session (if applicable for the session type) and refreshes the state of the session if it is incorrect. This command queries the states of the copy sets on the hardware. You are not required to run this command under typical circumstances; Copy Services Manager refreshes the states of its sessions through multiple means. However, if you discover an inconsistency between Copy Services Manager and the hardware, you can use this command to enable Copy Services Manager to update itself. This command triggers multiple queries on the hardware, which can impact hardware performance. Do not run this command more frequently than every few minutes in each session. This command is not available if the session is in the Defined state.
Set Production to Site 1	Allows you to set the production volume to be at Site 1 from the Defined state.
Set Production to Site 2	Allows you to set the production volume to be at Site 2 from the Defined state.
Start	Establishes all relationships in a single-direction session and begins the process necessary to start forming consistency groups on the hardware.
Start H1->H2	Starts copying data from H1 to H2 in a Global Mirror Failover/Failback session. Establishes the necessary relationships in the session and begins the process necessary to start copying data from the H1 site to the H2 site and to start forming consistency groups.
Start H2->H1	Starts copying data from H2 to H1 in a failover and failback session for DS8000®. If a recover was performed on a session such that the production site is now H2, you can issue a Start H2->H1 command to start moving data back to Site 1. However, this start does not provide consistent protection as it copies only asynchronously back because of the long distance. A Global Copy relationship is used. When you are ready to move production back to Site 1, issue a suspend to the session. This action puts the relationships into a synchronized state and suspends them consistently. Sessions are consistent when a H2->H1 copy occurs for the FlashSystem/IBM Spectrum® Virtualize storage systems
StartGC H1->H2 This command is available only for Global Mirror Failover/Failback and Global Mirror Failover/Failback with Practice sessions.	Establishes Global Copy relationships between site 1 and site 2 and begins asynchronous data replication from H1 to H2. To change the session state from Preparing to Prepared, you must issue the Start H1->H2 command and the session must begin to form consistency groups. There is no disaster recovery protection for Global Copy relationships. If a disaster such as the loss of a primary storage system or a link failure between the sites occurs, the session might be inconsistent when you issue the Recover command. This command is available for the DS8000 storage system.
Stop	Inconsistently stops the pairs that are in a Global Copy mode.
Stop When Drained	After a StartGC command, the session is in a Preparing and Global Copy mode. The Stop When Drained command starts a thread that queries all pairs until zero pairs are out-of-sync (OOS). After the OOS for the pairs goes to zero, the Stop command is issued. Note: The Stop command is issued, rather than Suspend, so that this procedure can be used in cascaded environments. Suspend puts the pairs in Metro Mirror mode, which is not allowed if the source of the session is the target of another relationship.
Suspend	Pauses the Global Mirror master session, which causes the session to stop forming consistency groups, and suspends the H1 to H2 Global Copy pairs. Note: This action occurs only if the session is in Global Mirror mode. If the session is in Global Copy mode, the Suspend command attempts to consistently suspend the pairs by establishing the Global Copy pairs as Metro Mirror pairs. When these pairs all reach a Prepared state, a Freeze is then issued to have consistency at the remote site. If you are using a System Storage DS8000: The Suspend command invokes a pause command for IBM® DS8000. The pause command that is invoked depends on the IBM DS8000 microcode level. If the following conditions are true, the Suspend command invokes a command that is equivalent to the IBM DS8000 command pausegmir -withsecondary: All primary volumes that are in the session are on a IBM DS8000 storage system with a microcode level that includes the pause with secondary consistency option. To determine whether this option is available for your storage system, see the IBM DS8000 documentation for the microcode level that you are using. The pause with secondary consistency option is enabled on the storage system. If these conditions are not true, the Suspend command invokes a command that is equivalent to the IBM DS8000 command pausegmir. Both commands temporarily pause the formation of consistency groups after the current consistency group is formed. However, the command for a pause with secondary consistency creates a consistent data set on the secondary volumes. If you do not want to suspend the Global Copy pairs when a Global Mirror session is suspended, open the rmserver.properties file in the `install dir`\liberty\wlp\usr\servers\csmServer\properties directory on distributed systems, or the `path_prefix`/opt/IBM/CSM/wlp/usr/servers/csmServer/properties directory on z/OS®, and add the following property: `csm.server.sus_gc_pairs_on_gm_pause = false` Tip: The pause with secondary consistency option requires that the Global Copy pairs are suspended. If you do not want to use the pause with secondary consistency option for storage systems on which the option is enabled, set the csm.server.sus_gc_pairs_on_gm_pause property to false.
Terminate	Removes all physical copies and relationships from the hardware during an active session. If you want the targets to be data consistent before you remove their relationship, you must issue the Suspend command, the Recover command, and then the Terminate command.