Complete this task to correct the revertible states and FlashCopy
sequence numbers that require the use of the DS CLI commitflash command.
This is the fifth step in the Global Mirror failover recovery process unless
your corrections require the use of the revertflash DS CLI command.
In this case, the use of the revertflash command becomes your fifth
step.
You can use the
commitflash command only when your analysis
of the FlashCopy relationships reveals one of the following conditions:
- All the FlashCopy sequence numbers are equal and at least one of the FlashCopy
relationships is nonrevertible.
- The FlashCopy relationships exist as follows:
- Some of the FlashCopy relationships completed processing so that a consistent
group has been created. These FlashCopy relationships are no longer revertible.
- Some of the FlashCopy relationships have not completed creating a new
consistency group formation. These FlashCopy relationships are still in a
revertible state.
- All the FlashCopy relationships have the same FlashCopy sequence
number. This indicates that all the FlashCopy relationships belong in the
same consistency group.
The commit action keeps a FlashCopy relationship in its current
state and resets the revertible state to No. When the commitflash command
is processed, the data in these relationships is committed to the consistency
group to which it would have become a part before the disaster occurred.
Perform
the following step to correct the applicable FlashCopy relationships. The
example command in this task is shown in two formats. The first format shows
the type of information that the command requires. The second format provides
the command with declared values for the variables.
Issue the commitflash command to correct the FlashCopy relationships
and commit them to the consistency group that was being formed before the
disaster occurred. Enter the commitflash command at the dscli command
prompt with the following parameters and variables: dscli>commitflash
-dev storage_image_ID SourceVolumeID
Example
dscli>commitflash -dev IBM.1750-68FA150 0100
Notes: - Remember that the storage_image_ID is the value for the remote
server that has been designated the primary server until the original primary
server is available for use.
- Global Mirror operations have performed the establish FlashCopy revertible
processing as the Global Mirror operations were trying to form a consistency
group before the disaster occurred. If your analysis, through use of the lsflash command,
has determined that a commitflash command is required,
then there is no need to issue a new mkflash command.
A confirmation message like the following one is generated
for each FlashCopy relationship that has been successfully reset.
FlashCopy pair 0100:0200 successfully committed.
After all the FlashCopy relationships have been corrected, you are
ready to use the fast reverse restore process, which is the next step in the
Global Mirror disaster recovery process.