HP Surestore E Disk Array XP256 HP XP P9000 External Storage Access Manager Us - Page 72

Suspended volume pair troubleshooting

Get HP Surestore E Disk Array XP256 PDF manuals and user guides View all HP Surestore E Disk Array XP256 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 72 highlights

Suspended volume pair troubleshooting A suspended volume pair is a pair in which normal data replication is not occurring between the primary and secondary volumes. Until the failure or condition that caused the suspension is resolved, production data on the primary volume is not copied to the secondary volume. A number of failures or conditions can cause a volume pair to become suspended, including: • Power supply failure • Secondary storage system failure • Communication failure between the primary and secondary storage systems • I/O failures • Quorum disk failure • Incompatible host mode option settings • Incomplete initial copy operation The troubleshooting procedures you use to resolve suspended volume pairs depends on the interface you are using when the pair becomes suspended. • When using RWC • When using RAID Manager The workflow for troubleshooting suspended pairs when using Remote Web Console Use the following process to resolve suspended volume pairs when using RWC: • Checking the pair status on the Detailed Information dialog box. • Following the troubleshooting steps based on the suspend type and the volume type (primary or secondary). The following table lists the troubleshooting steps to use for each suspend type and volume type. Suspend type VOL Type PSUE, by RCU P-VOL S-VOL PSUE, P-VOL S-VOL Failure S-VOL PSUE, P-VOL S-VOL Failure S-VOL 72 Troubleshooting Error Corrective action The primary storage system detected Clear the error condition at the secondary an error condition at the secondary storage system or S-VOL, then resynchronize storage system which caused the the pair from the primary storage system. primary storage system to suspend the pair. The S-VOL suspend type is S-VOL Failure. The primary storage system detected an error during communication with the secondary storage system, or an I/O error during update copy. The suspend type for the S-VOL is usually S-VOL Failure. Do the following: • Check data path status on the secondary storage system Status dialog box. Clear any errors. • Clear any error conditions on the secondary storage system or S-VOL. • After errors are cleared, resynchronize from the primary storage system. The primary storage system detected a failure in the quorum disk. Do the following: • Recover the quorum disk failure by following the recovery procedure defined by the external storage system. • If SIMs related to External Storage are issued, call the HP Support Center and follow the recovery procedure defined by the HP XP P9000 External Storage for Open and Mainframe Systems User Guide. After the failure is recovered,

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
Suspended volume pair troubleshooting
A suspended volume pair is a pair in which normal data replication is not occurring between the
primary and secondary volumes. Until the failure or condition that caused the suspension is resolved,
production data on the primary volume is not copied to the secondary volume.
A number of failures or conditions can cause a volume pair to become suspended, including:
•
Power supply failure
•
Secondary storage system failure
•
Communication failure between the primary and secondary storage systems
•
I/O failures
•
Quorum disk failure
•
Incompatible host mode option settings
•
Incomplete initial copy operation
The troubleshooting procedures you use to resolve suspended volume pairs depends on the interface
you are using when the pair becomes suspended.
•
When using RWC
•
When using RAID Manager
The workflow for troubleshooting suspended pairs when using Remote Web Console
Use the following process to resolve suspended volume pairs when using RWC:
•
Checking the pair status on the
Detailed Information
dialog box.
•
Following the troubleshooting steps based on the suspend type and the volume type (primary
or secondary).
The following table lists the troubleshooting steps to use for each suspend type and volume type.
Corrective action
Error
VOL Type
Suspend type
Clear the error condition at the secondary
storage system or S-VOL, then resynchronize
the pair from the primary storage system.
The primary storage system detected
an error condition at the secondary
storage system which caused the
P-VOL
S-VOL
PSUE,
by RCU
primary storage system to suspend the
pair. The S-VOL suspend type is S-VOL
Failure.
Do the following:
The primary storage system detected
an error during communication with
P-VOL
S-VOL
PSUE,
S-VOL Failure
•
Check data path status on the secondary
storage system
Status
dialog box. Clear
any errors.
the secondary storage system, or an
I/O error during update copy.
The suspend type for the S-VOL is
usually S-VOL Failure.
•
Clear any error conditions on the
secondary storage system or S-VOL.
•
After errors are cleared, resynchronize
from the primary storage system.
Do the following:
The primary storage system detected
a failure in the quorum disk.
P-VOL
S-VOL
PSUE,
S-VOL Failure
•
Recover the quorum disk failure by
following the recovery procedure defined
by the external storage system.
•
If SIMs related to External Storage are
issued, call the HP Support Center and
follow the recovery procedure defined by
the
HP XP P9000 External Storage for
Open and Mainframe Systems User
Guide
. After the failure is recovered,
72
Troubleshooting