Metro Mirror - Metro Mirror commands

Edit online

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

Table 1. Metro Mirror - Metro Mirror commands
Command	Action
Confirm Production at Site 1	Confirms that you want to establish site 1 as the production site after you issue suspend and recover commands for the session.
Confirm Production at Site 2	Confirms that you want to establish site 2 as the production site after you issue suspend and recover commands for the session.
Confirm Production at Site 3	Confirms that you want to establish site 3 as the production site after you issue suspend and recover commands for the session.
FailoverH1	Completes a failover operation to the H1 target site. This command enables read and write access to the target volumes. At the same time, it maintains a recording of changes to the volumes that prevents a full copy when the relationship is restarted. You can use this command to practice your disaster recovery capabilities without initiating a site switch. To switch sites, the RecoverH1 command is required.
FailoverH2	Completes a failover operation to the H2 target site. This command enables read and write access to the target volumes. At the same time, it maintains a recording of changes to the volumes that prevents a full copy when the relationship is restarted. You can use this command to practice your disaster recovery capabilities without initiating a site switch. To switch sites, the RecoverH2 command is required.
FailoverH3	Completes a failover operation to the H3 target site. This command enables read and write access to the target volumes. At the same time, it maintains a recording of changes to the volumes that prevents a full copy when the relationship is restarted. You can use this command to practice your disaster recovery capabilities without initiating a site switch. To switch sites, the RecoverH3 command is required.
HyperSwap H1	Triggers a HyperSwap operation where I/O is redirected from the source volume to the target volume H1, without affecting the application that is using those volumes.
HyperSwap H2	Triggers a HyperSwap operation where I/O is redirected from the source volume to the target volume H2, without affecting the application that is using those volumes.
HyperSwap H3	Triggers a HyperSwap operation where I/O is redirected from the source volume to the target volume H3, without affecting the application that is using those volumes.
RecoverH1	Recovers the session to the H1 target site. This command makes the target host volumes consistent and available for access as the new production site. Upon completion of this command, the session becomes Target Available.
RecoverH2	Recovers the session to the H2 target site. This command makes the target host volumes consistent and available for access as the new production site. Upon completion of this command, the session becomes Target Available.
RecoverH3	Recovers the session to the H3 target site. This command makes the target host volumes consistent and available for access as the new production site. Upon completion of this command, the session becomes Target Available.
Re-enable Original Direction	Sets the production site back to the original site and reenables the start commands in the original direction. You can use this command after you issue the suspend, recover, and confirm commands.
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.
Release I/O	Enables the source volume to receive data after a copy relationship is suspended. This command is not displayed if the Release I/O after Suspend property is selected for the session.
Set Production to Site 1	Establishes Site 1 as the production site while the session is in the Defined state. After you issue this command, the Start H1->H2 and Start H1->H3 commands become available.
Set Production to Site 2	Establishes Site 2 as the production site while the session is in the Defined state. After you issue this command, the Start H2->H1 and Start H2->H3 commands become available.
Set Production to Site 3	Establishes Site 3 as the production site while the session is in the Defined state. After you issue this command, the Start H3->H1 and Start H3->H2 commands become available.
Start	Establishes Metro Mirror relationships between the volumes on the production site and the volumes at the other sites in the session, and begins data replication to those sites. For example, if Site 1 is the production site, data replication occurs between the H1 and H2 volumes and the H1 and H3 volumes at the same time.
Start H1->H2	Establishes Metro Mirror relationships between the H1 volumes and the H2 volumes, and begins data replication from H1 to H2.
Start H1->H3	Establishes Metro Mirror relationships between the H1 volumes and the H3 volumes, and begins data replication from H1 to H3.
Start H2->H1	Establishes Metro Mirror relationships between the H2 volumes and the H1 volumes and starts data replication from H2 to H1.
Start H2->H3	Establishes Metro Mirror relationships between the H2 volumes and the H3 volumes and starts data replication from H2 to H3.
Start H3->H1	Establishes Metro Mirror relationships between the H3 volumes and the H1 volumes and starts data replication from H3 to H1.
Start H3->H2	Establishes Metro Mirror relationships between the H3 volumes and the H2 volumes and starts data replication from H3 to H2.
StartGC	Establishes Global Copy relationships between the volumes on the production site and the volumes at the other sites in the session, and begins asynchronous data replication to those sites. For example, if Site 1 is the production site, data replication occurs between the H1 and H2 volumes and the H1 and H3 volumes at the same time. The session remains in the Preparing state until you issue a Start, Suspend, or Terminate command.
StartGC H1->H2	Establishes Global Copy relationships between the H1 volumes and the H2 volumes, and begins asynchronous data replication from H1 to H2. The session remains in the Preparing state until you issue a Start, Suspend, or Terminate command.
StartGC H1->H3	Establishes Global Copy relationships between the H1 volumes and the H3 volumes, and begins asynchronous data replication from H1 to H3. The session remains in the Preparing state until you issue a Start, Suspend, or Terminate command.
StartGC H2->H1	Establishes Global Copy relationships between the H2 volumes and the H1 volumes, and begins asynchronous data replication from H2 to H1. The session remains in the Preparing state until you issue a Start, Suspend, or Terminate command.
StartGC H2->H3	Establishes Global Copy relationships between the H2 volumes and the H3 volumes, and begins asynchronous data replication from H2 to H3. The session remains in the Preparing state until you issue a Start, Suspend, or Terminate command.
StartGC H3->H1	Establishes Global Copy relationships between the H3 volumes and the H1 volumes, and begins asynchronous data replication from H3 to H1. The session remains in the Preparing state until you issue a Start, Suspend, or Terminate command.
StartGC H3->H2	Establishes Global Copy relationships between the H3 volumes and the H2 volumes, and begins asynchronous data replication from H3 to H2. The session remains in the Preparing state until you issue a Start, Suspend, or Terminate command.
Stop	Stops updates to all the target volumes of the pairs in a session. The following information applies to this command and the following Stop commands: Targets are not consistent after the stop. You can issue the command at any point during an active session.
StopH1H2	Stops updates from H1 to H2 volumes in a session.
StopH1H3	Stops updates from H1 to H3 volumes in a session.
StopH2H1	Stops updates from H2 to H1 volumes in a session.
StopH2H3	Stops updates from H2 to H3 volumes in a session.
StopH3H1	Stops updates from H3 to H1 volumes in a session.
StopH3H2	Stops updates from H3 to H2 volumes in a session.
Suspend	Suspends updates to all the target volumes of the pairs in a session. The following information applies to this command and the following Suspend commands: You can issue the command at any point during an active session. Avoid use of the same LSS pairs for multiple Metro Mirror sessions. Metro Mirror uses a freeze command on DS8000® storage systems to create the data-consistent point. If other Metro Mirror sessions overlap the same LSS pairs as in this session, those sessions are also suspended. When a Suspend command is issued to a source volume in an LSS that has source volumes in another active Metro Mirror session, the other source volumes are affected only if they have the same target LSS. The primary volumes are suspended, but volumes in the same source LSS that have target volumes in a different LSS are not affected because they use a different PPRC path connection.
SuspendH1H2	Suspends updates from H1 to H2 volumes in a session.
SuspendH1H3	Suspends updates from H1 to H3 volumes in a session.
SuspendH2H1	Suspends updates from H2 to H1 volumes in a session.
SuspendH2H3	Suspends updates from H2 to H3 volumes in a session.
SuspendH3H1	Suspends updates from H3 to H1 volumes in a session.
SuspendH3H2	Suspends updates from H3 to H2 volumes in a session.
Terminate	Removes all copy relationships from the hardware during an active session. If you want the targets to be data consistent before you remove their relationship, issue the following commands before you issue the Terminate command: Suspend RecoverHx Where x is the site to which you want to recover.
TerminateH1H2	Removes all H1`>`H2 or H2`>`H1 relationships from the hardware during an active session. If you want the target to be data consistent before you remove their relationship, issue the following commands before you issue the Terminate command: SuspendH1H2 Recoverx Where x is the site to which you want to recover.
TerminateH1H3	Removes all H1`>`H3 or H3`>`H1 relationships from the hardware during an active session. If you want the target to be data consistent before you remove their relationship, issue the following commands before you issue the Terminate command: SuspendH1H3 Recoverx Where x is the site to which you want to recover.
TerminateH2H3	Removes all H2`>`H3 or H3`>`H2 relationships from the hardware during an active session. SuspendH2H3 Recoverx Where x is the site to which you want to recover.