Complete this task to check the status of your Global Mirror transactions
before processing ends as a result of a disaster. Normally, this is the second
step in the Global Mirror failover recovery process because in a rolling disaster,
your primary server is still operational. This might be the first step if
your primary server is not operational.
You must end Global Mirror processing before you can initiate this
task.
You must determine the status of the Global Mirror processing
before processing was ends. Some transactions might be half completed while
others are not yet started. Querying the status of your transactions provides
a basis for planning which tasks must be done next. The situation you face
is similar to one of the following conditions:
- When Global Mirror processing ends, the formation of a consistency group
is in progress and the FlashCopy state between the B and the C volumes in
the remote storage server is not the same for all relationships.
- Some FlashCopy pairs might have completed the FlashCopy phase of Global
Mirror processing to form a new consistency group and might have already committed
the changes.
- Some FlashCopy pairs might not have completed and are in the middle of
processing to form their consistent copy and remain in a revertible state.
- There is no master server that controls and coordinates the processing
that might continue for a brief period at the remote site.
Perform the following steps to obtain an initial status of your
transactions.
- If your primary server is still operational, issue the lssession and lspprc commands
to obtain reports that allow you to determine the status of your Global Mirror
transactions. If your primary server is not available, go to the next step.
- Gain access to your remote server and navigate to the directory
where you installed the DS CLI application.
- Log in to a DS CLI session.
- Issue the lspprc command to provide a report that allows
you to determine the status of your Global Mirror transactions.
Enter
the
lspprc command at the dscli command prompt with the following parameters
and variables:
dscli>lspprc -dev storage_image_ID -remotedev storage_image_ID -l
SourceVolumeID:TargetVolumeID
Example
dscli>lspprc -dev IBM.1750-68FA120 -remotedev IBM.1750-68FA150 -l
0100-0103:0100-0103 0200:0200 0300-0303:0300-0303
Note: The report
displays your Global Copy pairs with a suspended state.
After you obtain your reports, you are ready for the next step in
the Global Mirror disaster recovery process, which is to issue the failover
command.