Metro Mirror - Global Mirror with Practice commands

Edit online

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

Table 1. Metro Mirror - Global Mirror with Practice 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, 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, 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, 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.
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.
Flash
This command is available in the following states:
  • Prepared state when the active host is H1 and data is copying H1 to I3
  • Prepared state when the active host is H2 and data is copying H2 to I3

If you issue a Flash command on a Global Mirror with Practice session for DS8000®, it temporarily pauses the formation of consistency groups. Ensure that all I3s are consistent, and then flash the data from I3 to the H3 volumes. After the flash is complete, the Global Mirror session automatically restarts, and the session begins forming consistency groups on I3. You can then use the H3 volumes to practice your disaster recovery procedures.
Allow Practice Flash Issued to allow a Flash operation again on a Practice session after it has been suspended with the Prevent Reflash of Practice volume after Flash or Recover option.

The Allow Practice Flash command appears in the Preparing or Prepared states only if it is currently preventing the reflash. If the session is Preparing, the Flash command does not display until the session gets to the Prepared state.

See Prevent a reflash when practicing disaster recovery for more information on using this command.
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 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.
ResumeGM Resumes the Global Mirror master session on the hardware allowing the hardware to restart all relationships and consistency group formation. The command does not do any of the additional checks such as establishing for logical paths, etc. that are run by issuing the Start command. This command is only recommended to be used when the session is suspended for a short amount of time, such as when creating a FlashCopy® or Safeguarded Copy backup at the remote site.
Note: The command does not work for sessions that are suspended and share the same consistency group on the hardware. When sessions share a consistency group, the Suspend command removes the volumes of the suspended session out of the hardware session in order to allow other sessions to continue to form consistency groups. So the ResumeGM command will not cause the pairs in the suspended session to be restarted, you must run the Start command for the same.
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 Site 1 Start 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 Site 2 Start 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 StartGC H3->H1->H2 and StartGC H3->H2->H1 commands become available.
Start H1->H2, H1->H3 Establishes Metro Mirror relationships between H1 and H2 volumes, and Global Mirror relationships between H1 and H3, and starts forming consistency groups. This relationship includes the J3 volume to complete the Global Mirror configuration.
Start H1->H2->H3 Establishes Metro Mirror relationships between H1 and H2, and Global Mirror relationships between H2 and H3. The Start H1->H2->H3 command can be used to transition from a multi-target configuration to a cascaded configuration. You can only transition from multi-target to cascaded if the Global Mirror leg is suspended.
Start H1->H2 Establishes Metro Mirror relationships between the H1 volumes and the H2 volumes, and begins data replication from H1 to H2.
Start GM H1->H3 Establishes a Global Mirror relationship between H1 and H3, and starts forming consistency groups. The relationship includes the J3 volume to complete the Global Mirror configuration.
Start H2->H1, H2->H3 Establishes Metro Mirror relationships between H2 and H1 volumes, and Global Mirror relationships between H2 and H3, and starts forming consistency groups. This relationship includes the J3 volume to complete the Global Mirror configuration.
Start H2->H1 Establishes Metro Mirror relationships between the H2 volumes and the H1 volumes and starts data replication from H2 to H1.
Start GM H2->H3 Establishes a Global Mirror relationship between H2 and H3, and starts forming consistency groups. The relationship includes the J3 volume to complete the Global Mirror configuration.
StartGC H1->H2, H1->H3

Establishes Global Copy relationships between the H1 and H2 volumes and between H1 and H3 volumes, and begins asynchronous data replication from H1 to H2 and H1 to H3.

The session remains in the Preparing state until you issue a Start, Suspend, Stop, 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, H2->H3

Establishes Global Copy relationships between the H2 and H1 volumes and between H2 and H3 volumes, and begins asynchronous data replication from H2 to H1 and H2 to H3.

The session remains in the Preparing state until you issue a Start, Suspend, Stop, 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, Stop, 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, Stop, or Terminate command.
StartGC H3->H1->H2

Establishes Global Copy relationships between the H3 volumes, and the H1 volumes, and H2 volumes, and begins asynchronous data replication from H3 to H1 and H2.

The session remains in the Preparing state until you issue a Suspend, Stop, or Terminate command.
StartGC H3->H2->H1

Establishes Global Copy relationships between the H3 volumes, and the H2 volumes, and the H1 volumes, and begins asynchronous data replication from H3 to H2 and H1.

The session remains in the Preparing state until you issue a Suspend, Stop, or Terminate command.
Stop

Stops updates to all the target volumes of the pairs in a session.

Targets are not consistent after the stop.
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.
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 the 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.
Suspend When Drained Suspends the session after all I/O drains to the tertiary site and marks all volumes at all sites as consistent. All I/O must be quiesced before you issue this command.
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.
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.
TerminateH3I3 Removes the FlashCopy relationships after a Flash command is issued. When you use Extent Space Efficient (ESE) volumes for your practice volumes (H3), it is recommended to set the No Copy option on the H3I3 role pair. When No Copy is set, data will only be physically written to H3 when a track is updated on I3. If the practice copy of the data is no longer needed, this command can be run to remove the FlashCopy relationship from I3 to H3, to prevent the relationship from consuming backend space.
Notes:
  • If the command is issued, H3 will no longer hold a consistent logical copy of the data until the next Flash or Recover is issued.
  • This command is only available for DS8000 practice sessions while in the Preparing, Prepared, or Suspended states. This command is not available while in the Defined or Target Available states.

Example: Set the production site and starting a Metro Mirror copy to both targets

In this example, the production site is site 1 and H1>H2 and H1>H3 are in the Defined state. To change to the production site to site 3 and start a Metro Mirror copy to both H1 and H2, issue the commands in the order that is presented:
  1. Set Production to Site 3
  2. Start

Example: Set the production site and starting a Global Copy to both targets

In this example, the production site is site 1 and H1>H2 and H1>H3 are in the Defined state. To change to the production site to site 3 and start a Global Copy to both H1 and H2, issue the commands in the order that is presented:
  1. Set Production to Site 3
  2. Start GC

Example: Set the production site and starting a Metro Mirror copy to a single target

In this example, the production site is site 1 and H1>H2 and H1>H3 are in the Defined state. To change to the production site to site 3 and start a Metro Mirror copy only to H2, issue the commands in the order that is presented:
  1. Set Production to Site 3
  2. Start H3->H2

Example: Set the production site and starting Metro Mirror copy to one target and a Global Copy to the second target

In this example, the production site is site 1 and H1>H2 and H1>H3 are in the Defined state. To change the production site to site 3 and start a Metro Mirror copy to H2 and a Global Copy to H1, issue the commands in the following order:
  1. Set Production to Site 3
  2. Start H3->H2
  3. Start GC H3->H1

Example: Change the production site after you recover to the site

In this example, the production site is site 1 and H1>H2 and H1>H3 are active. To recover to site 2 and confirm the production site as site 2, issue the following commands:
  1. Suspend
  2. RecoverH2
  3. Confirm Production at Site 2

Example: Reenable the original production site

In this example, the production site is site 2 and H2>H1 and H2>H3 are active after issuing the commands in the preceding example. To re-enable H1 as the production site, issue the Re-enable Original Direction command.

Example: Complete a failover to a single target for practice

In this example, the production site is site 1 and H1>H2 and H1>H3 are active. To fail over to site 3, issue the following commands in the order that is presented:
  1. SuspendH1H3
  2. FailoverH3
If the production site is site 2 and H2>H1 and H2>H3 are active, issue the following commands to fail over to site 3:
  1. SuspendH2H3
  2. FailoverH3

Example: Suspend the copy of data to both target sites

In this example, the production site is site 1 and H1>H2 and H1>H3 are active. To suspend the copy of data to both target sites, issue the Suspend command.

Example: Suspend the copy of data to a single target site

In this example, the production site is site 1 and H1>H2 and H1>H3 are active. To suspend the copy of data only from H1 to H3, issue the SuspendH1H3 command.

Example: Stop the copy of data to both target sites

In this example, the production site is site 1 and H1>H2 and H1>H3 are active. To stop the copy of data to both target sites, issue the Stop command.

Example: Stop the copy of data to a single target site

In this example, the production site is site 1 and H1>H2 and H1>H3 are active. To stop the copy of data only from H1 to H3, issue the StopH1H3 command.