HP XP Continuous Access Software - Manual (Page 223)

Table 44 Resolving XP Continuous Access Journal Pair Suspension
Recovery Procedure SIM Causes of Suspension Classification
According to the SIM, remove the
hardware blockade or failure.
Restore the failed volume pairs
(Pairresync).
If a failure occurs during execution of
the RAID Manager
horctakeover
command, secondary volumes in
SSWS pair status may remain in the
master journal group. If these volumes
remain, execute the pairresync -swaps
command on the secondary volumes
whose pair status is SSWS (pairresync
is the RAID Manager command for
resynchronizing pair and -swaps is a
swap option). This operation changes
all volumes in the master journal group
to primary volumes. After this
operation, restore the volume pairs
(Pairresync).
DC0x
DC1x
DC2x
Hardware redundancy has been lost
due to a blockade condition. As a
result, one of the following operations
could not be completed:
primary-secondary storage system
communications, journal creation, copy
operation, restore operation, staging
process, or de-staging process.
Journals cannot be retained because
some portion of the cache memory or
the shared memory has been blocked
due to hardware failure.
The primary storage system failed to
create and transfer journals due to
unrecoverable hardware failure.
The secondary storage system failed
to receive and restore journals due to
an unrecoverable hardware failure.
The drive parity group was in
correction-access status while the XP
Continuous Access Journal pair was in
COPY status.
Primary storage
system hardware
or secondary
storage system
hardware
Remove the failure from the primary
and secondary storage systems or the
network relay devices.
If necessary, increase resources as
needed (for example, the amount of
cache, the number of paths between
primary and secondary storage
systems, the parity groups for journal
volumes).
Restore the failed pairs (Pairresync).
DC0x
DC1x
Communications between the storage
systems failed because the secondary
storage system or network relay
devices were not running.
Journal volumes remained full even
after the timeout period elapsed.
Communications
between the
primary and
secondary
storage systems
Release the failed pairs (pairsplit-S).
If necessary, increase resources as
needed (for example, the amount of
cache, the number of paths between
primary and secondary storage
systems, the parity groups for journal
volumes).
Re-establish failed pairs (Paircreate).
DC2x An unrecoverable RIO (remote I/O)
timeout occurred because the storage
system or network relay devices were
overloaded. Or, the RIO could not be
finished due to a failure in the storage
system. RIO overload or
RIO failure
No recovery procedure is required.
The primary storage system
automatically removes the suspension
condition when the storage system is
powered on. DC8x The XP Continuous Access Journal pairs
were temporarily suspended due to a
planned power outage to the primary
storage system. Planned power
outage to the
primary storage
system
Checking XP Continuous Access Journal Error Codes
Remote Web Console computers display an error message when an error occurs during XP
Continuous Access Journal operations. The error message describes the error and provides an
error code consisting of four digits. The error message may also include an SVP error code. If you
need to call HP technical support for assistance, report the error code(s). See the HP StorageWorks
XP24000/XP20000 Remote Web Console Error Codes for a list of error codes that may appear
on the Remote Web Console computers.
Checking XP Continuous Access Journal Error Codes 223