Continuous access xp journal error codes, Calling hp, Table 57 – HP XP Continuous Access Software User Manual
Page 219

Table 57 Resolving Continuous Access XP Journal pair suspension
Classification
Causes of suspension
SIM
Recovery procedure
Primary array
hardware or
secondary array
hardware
Hardware redundancy was lost due
to some blockade condition. As a
result, one of the following could not
complete: primary-secondary array
communications, journal creation,
copy operation, restore operation,
staging process, or de-staging
process.
Journals cannot be retained because
some portion of cache memory or
shared memory was blocked due to
hardware failure.
Primary array failed to create
and transfer journals due to
unrecoverable hardware failure.
Secondary array failed to receive
and restore journals due to
unrecoverable hardware failure.
Drive parity group was in
correction-access status while
the Continuous Access XP Journal
was in COPY status.
DC0x
DC1x
DC2x
According to SIM, remove the
hardware blockade or failure.
Restore the failed volume pairs
(Pairresync).
DIf a failure occurs during execution
of the CCI 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 CCI 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).
Communication
between the
primary and
secondary arrays
Communication between arrays
failed because the secondary array
or network relay devices were not
running.
Journal volumes remained full even
after the timeout period elapsed.
DC0x
DC1x
Remove the failure from the primary
and secondary arrays or network
relay devices.
If necessary, increase resources as
needed (for example, amount of
cache, number of paths between
primary and secondary arrays, and
parity groups for journal volumes).
Restore the failed pairs (Pairresync).
RIO overload or
RIO failure
Unrecoverable RIO (remote I/O)
timeout occurred because the array
or networks relay devices were
overloaded.
RIO could not be finished due to a
failure in the array.
DC2x
Delete failed pairs (pairsplit-S).
If necessary, increase resources as
needed (for example, amount of
cache, number of paths between
primary and secondary arrays, and
parity groups for journal volumes).
Re-establish failed pairs (Pairresync).
Planned power
outage to the
primary array
Continuous Access XP Journal pairs
were temporarily suspended due
to a planned power outage to the
primary array.
DC8x
None. Primary array automatically
removes the suspension condition
when the array is powered on.
Continuous Access XP Journal error codes
The Command View XP management station or XP Remote Web Console displays an error message
when an error occurs during Continuous Access XP Journal operations. The error message describes
the error and displays an error code consisting of four digits. The error message might also include a
local array SVP error code. If you need to contact your HP account support representative for assistance,
report the error codes.
Calling HP
If you need to call you HP account support representative, provide as much information about the
problem as possible, including:
Continuous Access XP Journal user guide
219