Migration commands
Use this information to learn about commands available for Migration sessions. To issue a command, go to and click the command.
| Command | Action |
|---|---|
| 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. |
| Recover | Issues the Recover command to suspended sessions. This command performs the steps necessary to make the target available to writes from an attached host as the new primary site. |
| Stop | Inconsistently suspends updates to all the targets of pairs in a session. This
command can be issued at any point during the copying of an active session. Note: Targets after the
suspend are not considered to be consistent.
|
| StartGC H1->H2 |
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. |
| StartGC H1->H2 With NoCopy | Establishes Global Copy relationships between site 1 and site 2 in
asynchronous mode without performing an initial copy of the data. 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. Note: This command should only be used when it is known that the data on the
volumes at site 1 are exactly the same as the data on the volumes at site 2. Only changes after the
establish will be copied to the secondary volumes.
|
| 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 | Causes all target volumes to remain at a data-consistent point and stops all
data that is moving to the target volumes. This command can be issued at any point during a session
when the data is actively being copied. Note: Avoid using 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
there are other Metro Mirror sessions overlapping 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. |
| Move to MM and Suspend Consistently | This command is designed to suspend all asynchronous replication to a data
consistent point in time. The command will convert all Global Copy pairs to a Metro Mirror
Synchronous mode. Once all pairs have reached a Prepared state it will then issue a freeze command
to the hardware in order to suspend the replication to a data consistent point in time. Note: Converting the pairs to a Metro Mirror synchronous mode may cause i/o impact
if the replication is at distance. This command should only be used in cases such as a migration,
where the applications have already been brought offline, or at times when the sources can tolerate
the synchronous replication and freeze issued for consistency.
|
| Terminate | Removes all copy relationships from the hardware during an active session. If you want the targets to be data consistent before removing their relationship, you must issue the Suspend command, then the Recover command, and then the Terminate command. |
| Validate for Secondary Migration | Use this command to validate that all the H1 volumes in the Migration session are targets of a Global Copy/Metro Mirror relationship on the hardware. The relationships must be in an active state and not in a suspended or failed over state. |
| Prepare for Secondary Migration | Issue this command when you are ready to perform the migration and more than 99% of the data has been copied to the new cascaded secondary volumes. This command queries the hardware to ensure that all the H1 volumes are targets of an existing Global Copy/Metro Mirror relationship. |
| Migrate Secondary | Use this command to migrate a secondary storage system to a newer storage
system. This command is available for the DS8000 storage system. |
| Sync and Swap | This command sends a command to the IOS component on z/OS to drive all the pairs to Metro Mirror mode. After all the pairs reach a Duplex state, IOS automatically performs a HyperSwap from the primary volumes to the volumes on the new storage system. |
| Sync | This command sends a command to the IOS component on z/OS to drive all the pairs to Metro Mirror mode. After you issue the command, the session goes into a Preparing to Swap state. |
| Swap | This command sends a command to the IOS component on z/OS to perform a HyperSwap from the primary volumes to the volumes on the new storage system. |
| Unfence and Clip | Use this command to remove the soft fence and clip the volumes to prevent an IPL from these volumes after the soft fence is removed. |
| Undo Clip | Use this command to unclip the volumes that were clipped by issuing the Unfence and Clip command. |