To Next PageTo Next Page
Why is HP XP P9500 Software monitoring data not updating?
If the HP Software monitoring data isn't updating, even with the Monitoring Switch enabled, disable the Monitoring Switch and then re-enable it again. This may be due to a change in the time setting of SVP. For more information on Monitoring Switch, see the HP P9000 Performance for Open and Mainframe Systems User Guide.
What to do if there is a problem with HP XP P9500 Remote Web Console?
To resolve issues with the HP Software Remote Web Console or Continuous Access Synchronous Z, ensure the problem isn't with your PC or LAN hardware/software. Restart the PC and attempt reconnecting to the storage system.
What to do if the status of pairs and/or logical paths is not displayed correctly in HP XP P9500?
Make sure that the correct CU image is selected. Check whether you selected correct items or options in Cnt Ac-J windows, such as the DKC Operation window, the Pair Operation window, and the Display Filter dialog box.
What to do if HP XP P9500 Software suspends pair during initial copy?
If the main HP Software system suspended this pair during the initial copy operation and the data on the R-VOL is not identical to the data on the M-VOL, release the pair from the main system. Clear all error conditions on the main system, M-VOL, remote system, and R-VOL. Re-create the pair.
What to do if HP XP P9500 shows 'Communication error'?
A timeout error has occurred in the path between the primary and secondary systems. Delete the failed path and retry.
What does HP Software 'Secondary Data Volume Failure' mean?
The message 'Secondary Data Volume Failure' in HP Software means that the primary system detected an error during communication with the secondary system or detected an I/O error during update copy. Clear any error conditions at the secondary system and the S-VOL. If you need to access the S-VOL, release the pair from the secondary system. If data in the S-VOL has been changed, release the pair from the primary system and then re-create the pair. If data in the S-VOL has not been changed, restore the pair from the primary storage system.
What does HP XP P9500 'This path was not established' mean?
The message 'This path was not established' in HP Software indicates that the specified path has not been successfully created or configured. Delete the failed path. You may need to change the minimum paths setting or delete the secondary system in order to delete the path. After deletion finishes, add the path and the secondary system by using the Add Path or Add DKC command.
What does HP Software 'Logical Blockade' mean and how to fix it?
A 'Logical Blockade' in HP Software indicates a failure at a primary or secondary system port, in the path relay equipment, or a broken connection cable. If the failure is at a primary system port, repair the port status on the primary system. If the failure is at a secondary system port, repair the port status on the secondary system, then delete the path and add the path and the secondary system back again. If the failure is in the path relay equipment, repair the path relay equipment, then delete the path and add the path and the secondary system back. If the connection cable is physically broken, replace the broken cable, then delete the path and add the path and the secondary system again.
What does HP XP P9500 'Pair-Port Type Mismatch' mean?
The 'Pair-Port Type Mismatch' error in HP Software means that the specified port in the secondary system is not configured as an RCU Target port. Make sure that the specified port in the secondary system is configured as an RCU target port.
What to do when HP Software shows 'Communication Failed'?
If HP Software shows 'Communication Failed', it means the primary system is connected to the secondary system successfully, but a logical communication timeout occurred. Make sure that the secondary system port and network relay devices (for example, cables and switches) are properly configured and functioning.
Explains the 4x4x4 Cascade configuration, combining 4x4 and 3DC Cascade configurations.
Describes Business Continuity Manager functions that support disaster recovery, including Reverse Resync and Consistency Preservation.
Explains how to define a 2DC configuration with one storage system installed at each site.
Details the procedure for defining a 3DC Cascade configuration.
Describes how to define a 3DC Multi-Target configuration.
Details how to define a 4x4 configuration.
Explains generating copy group definition files using comma-separated value (CSV) files.
Provides the step-by-step procedure for performing a failover.
Details the step-by-step procedure for performing a failback.
Provides troubleshooting steps for errors encountered with the delta resync function.
Explains procedures for primary site storage system maintenance.
Details procedures for local site storage system maintenance.
Details troubleshooting procedures for BCM Monitor issues.
Explains common system failures that might occur with Business Continuity Manager.
Describes the function that reports errors when volume status changes to an error state.
Provides procedures for recovering from various types of failures.
Outlines methods for performing operations when a copy group volume has a hardware failure.
General