HP StorageWorks XP24000 Continuous Access Journal Software User and Reference Guide, v01 (T5278-96001, June 2007)

Table 28 Resolving Continuous Access Journal Pair Suspension
Classification Causes of Suspension
SIM
Recovery P rocedure
Primary
storage system
hardware or
secondary
storage system
hardware
Hardware redundancy has been lost
due
to a blockade condition. As a
result, one of the following could
not
complete: 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 receiveand restorejournalsdue to
an
unrecoverable hardware failure.
The drive parity group was in
correction-access status while the
Continuous Access Journal pair was
in COPY status.
DC0x
DC1x
DC2x
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 secondar y volumes
whose pairstatusisSSWS(pairresync
is
the R AID 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).
Communica-
tions between
the
primary and
secondary stor-
age
systems
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.
DC0x
DC1x
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).
RIO o
verload or
RIO
failure
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 duetoafailureinthe
storage system.
DC2x
Relea
se the
failed pairs (pairsplit-S).
If
nec
essary, increase resources as
need
ed
(for example, the amount of
cach
e, the number of paths between
prim
ary and secondar y storage
systems, the parity groups for journal
volumes).
Re-establish failed pairs (Paircreate).
Planned power
outage to the
primary storage
system
The Continuous Access Journal pairs
were temporarily suspended due to a
planned power outage to the primary
storage system.
DC8x
No recovery procedure is required.
The primary storage system will
automatically remove the suspension
condition when the storage system is
powered on.
Checking Continuous Access Journal Err or Codes
Remote Web Console computers display an error message when an error occurs during Continuous
Access Journal operations. The error message describes the error and displays an error code consisting
of
four digits. The error message may also include a storage system SVP error code. If you need to call HP
technical support for assistance, report the error code(s). Please see HP StorageWorks XP24000 Remote
Web Console Error Codes for a list of error codes displayed on the Remote We b Console computers.
156
Troubleshooting