HP StorageWorks XP Remote Web Console Software User Manual

Page 220

Advertising
background image

Table 43 Troubleshooting Suspended XP Continuous Access Journal Pairs (continued)

Corrective Action

Description

Applies To

Suspend
Type

storage system performs an initial copy
operation in response to the pairresync

nonvolatile memory during the IMPL
procedure. This error occurs only if the

volume,
secondary

request, so that the entire primary data

primary storage system is without power

data
volume

volume is copied to the secondary data
volume.

for more than 48 hours (power failure
and fully discharged batteries).

Release the pair from the primary
storage system. Clear all error

The primary storage system suspended
this pair during the initial copy

Primary
data

PSUE,
Initial Copy
Failed

conditions for the primary storage

operation. The data on the secondary

volume,

system, primary data volume, secondary

data volume is not identical to the data
on the primary data volume.

secondary
data
volume

storage system, and secondary data
volume. Restart the initial copy
operation by using the Paircreate
window.

None. The primary storage system
automatically restores these XP

The primary storage system suspended
all XP Continuous Access Journal pairs

Secondary
data
volume

PSUE,
MCU
P/S-OFF

Continuous Access Journal pairs when

because the primary storage system was
powered off.

the primary storage system is powered
on.

“Resolving XP Continuous Access Journal Pair Suspension” (page 220)

provides troubleshooting

instructions for XP Continuous Access Journal pair suspension. Hardware failures that affect the
cache memory and the shared memory of the primary or secondary storage system may also cause
the XP Continuous Access Journal pairs to be suspended.

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.

DC0x

DC1x

Hardware redundancy has been lost
due to a blockade condition. As a
result, one of the following operations

Primary storage
system hardware
or secondary

Restore the failed volume pairs
(Pairresync).

DC2x

could not be completed:
primary-secondary storage system

storage system
hardware

If a failure occurs during execution of
the RAID Manager horctakeover

communications, journal creation, copy
operation, restore operation, staging
process, or de-staging process.

command, secondary volumes in
SSWS pair status may remain in the

Journals cannot be retained because
some portion of the cache memory or

master journal group. If these volumes
remain, execute the pairresync -swaps

the shared memory has been blocked
due to hardware failure.

command on the secondary volumes
whose pair status is SSWS (pairresync

The primary storage system failed to
create and transfer journals due to
unrecoverable hardware failure.

is the RAID Manager command for
resynchronizing pair and -swaps is a
swap option). This operation changes
all volumes in the master journal group

The secondary storage system failed
to receive and restore journals due to
an unrecoverable hardware failure.

to primary volumes. After this
operation, restore the volume pairs
(Pairresync).

The drive parity group was in
correction-access status while the XP
Continuous Access Journal pair was in
COPY status.

Remove the failure from the primary
and secondary storage systems or the
network relay devices.

DC0x

DC1x

Communications between the storage
systems failed because the secondary
storage system or network relay
devices were not running.

Communications
between the
primary and
secondary
storage systems

If necessary, increase resources as
needed (for example, the amount of

Journal volumes remained full even
after the timeout period elapsed.

cache, the number of paths between
primary and secondary storage

220 Troubleshooting

Advertising