Ending Global Mirror processing when a disaster occurs

Depending on the state of the local Global Mirror storage server, you might have an opportunity to end Global Mirror processing before you can initiate the rest of the recovery steps. Generally, a disaster affects your local server and your choices for ending Global Mirror processing in one of the following ways:

• Your site experiences a rolling disaster and your Global Mirror processing is not being done through a DS CLI script. This circumstance allows you time to issue a pause command, followed by a query command, and then an end Global Mirror processing command.
  Note: If the query displays a status of Fatal or a null (-), you must analyze and correct your consistency groups during the recovery process. If the query displays a status of Paused, your consistency groups are formed before you end Global Mirror processing.
• Your site experiences a rolling disaster and your Global Mirror processing is being done through a DS CLI script. You can take a chance that you have enough time to allow the script to process to the end. However, it is likely that you must end Global Mirror processing by pressing the CTRL C buttons on your keyboard because there is no pause feature when running a script.

  Because this is a rolling disaster, you might have time to log back into your DS CLI session on the local server and query the status of the Global Mirror processing before it was ended.

• Your sites' local server is affected by the disaster immediately and you have no time to end Global Mirror processing or issue a status query.