HP P9000 Business Continuity Manager User Guide

12 Troubleshooting
This chapter describes the troubleshooting procedures provided by Business Continuity Manager:
• “Troubleshooting Failures” (page 554)
• “Error Notification” (page 554)
• “Performance Monitor” (page 555)
• “Trace Output Method” (page 556)
• “Collecting Logs” (page 556)
• “HyperSwap Completion Detection” (page 568)
• “Recovering from a Failure” (page 569)
Troubleshooting Failures
Because Business Continuity Manager is frequently used in large-scale systems, a system failure
might cause a substantial problem.
The following are possible types of failure:
• Volume errors
• Line errors
• Hardware or software errors not included in the above
Table 99 (page 554) lists the functions provided by Business Continuity Manager to mitigate failures.
Table 99 Troubleshooting Functions
ObjectiveFunction
Reports errors by using a message or return code when a volume status changes to
an error status.
Error notification
Monitors events that might cause an error in the future. Provides information to help
prevent errors from occurring or identify the cause of an error after it has occurred.
Performance Monitor
Extracts trace information such as macros issued to the storage system to help find
the cause of errors when they occur.
Collecting trace
information
Stores traced information in log files. The logs for commands executed from the ISPF
panel and the CLI can also be collected.
Collecting logs
For 2DC configurations with HyperSwap and Cnt Ac-J Z, a HyperSwap is performed
for Cnt Ac-S Z copy groups with the HyperSwap attribute, and detected upon
completion.
HyperSwap
completion detection
Error Notification
BC Z, Cnt Ac-S Z, Cnt Ac-A, or Cnt Ac-J Z copy pairs enter an error status when an error occurs.
Business Continuity Manager supports a function that monitors this status transition and notifies
you of when a copy pair enters an error status.
Table 100 (page 555) lists the error statuses.
554 Troubleshooting