Continuous access xp journal suspend types, Table 6 – HP StorageWorks XP Remote Web Console Software User Manual

Page 35

Advertising
background image

Continuous Access XP Journal user guide

35

Continuous Access XP Journal suspend types

Table 7

describes the Continuous Access XP Journal suspend types, which indicate the reason for the

suspension. Continuous Access XP Journal pairs can be suspended by the primary or secondary array.

For more information, see

Continuous Access XP Journal suspension conditions” on page 36

.

The primary array suspends a Continuous Access XP Journal pair when it detects any of the following

suspension conditions:

You deleted the data volume pair from the secondary array

An error condition related to the secondary array, secondary data volume, or Continuous Access XP

Journal update copy operation

The primary array cannot communicate with the secondary array

A Continuous Access XP Journal suspension condition

When a Continuous Access XP Journal pair is suspended, the primary array stops performing journal

obtain operations for the pair. The primary array continues accepting write I/Os for the suspended

primary data volume and keeps track of the primary data volume cylinders/tracks updated while the pair

PSUS, Pairsplit-S

to RCU

Primary data volume

The primary array detected that the secondary data

volume’s status changed to SMPL because you deleted the

pair (pairsplit-S) from the secondary array. The pair cannot

be resumed because the secondary data volume does not

have the PSUS/PSUE status.

PSUS, JNL Cache

Overflow

Primary data volume,

Secondary data volume

The data volume pair was suspended because it was highly

likely that the journal data would overflow.

NOTE:

RAID Manager XP displays this split type as PFUS.

Table 6

Consistency status for split/suspended Continuous Access XP Journal secondary data volumes

Consistency status

(displayed at secondary

array)

Description

Volume

This Continuous Access XP Journal data volume pair was split or suspended alone.

Update sequence consistency between this secondary data volume and the other

secondary data volume in this journal group is not ensured. You cannot use the

secondary data volume for disaster recovery at the secondary site. This status is

indicated when:

You split the pair using the Suspend Range-Volume (LU) pairsplit option.

The pair was suspended due to a failure that did not affect the entire journal

group.

Group

This Continuous Access XP Journal data volume pair was split or suspended with the

other pairs in its journal group. Update sequence consistency between the secondary

data volume and other secondary data volumes in this journal group is ensured. You

can use this secondary data volume for disaster recovery at the secondary system

(after deleting the Continuous Access XP Journal data volume pair from the secondary

array). This status is indicated when:

You split the pair using the Suspend Range-Group pairsplit option.

All pairs in this journal group were suspended due to a failure that affected the

entire journal group, not just one pair (for example, a primary array-secondary

array communication failure).

One pair in the group was suspended due to a failure that did not affect the entire

group.

Table 5

Continuous Access XP Journal split types (PSUS) (continued)

Type

Applies to

Description

Advertising