HP StorageWorks XP Remote Web Console Software User Manual
Page 38
installed and operational for the XP disk array, this SIM results in an SNMP trap which indicates
the reason for suspension.
•
Universal Replicator for Mainframe Pair Status
The Universal Replicator for Mainframe Suspending and Deleting (release) transitional states
occur when a request to change the Universal Replicator for Mainframe pair status has been
accepted, but the change to the requested status (suspended or simplex) is not yet complete.
These states are not reported to the host. In the case of Suspending, both the user and the
primary storage system can request the status change. In the case of Deleting (release), only
the user can request the status change. If the user requested the status change, the final status
is reported at the end of the transition. If an error caused the status to change to suspended,
the suspended status is reported at the beginning of the transition.
After a storage system receives a request for splitting or releasing a pair in Flush mode, the
status of the pair will remain Suspending or Deleting until the journal in the master journal
group is restored into the restore journal group and the pair is completely split or released.
To calculate the time during which the pair remains Suspending or Deleting, use the following
equation:
C × (u ч 100) Ч 1,024 ч V (The unit is seconds)
where:
◦
C is the total capacity of the master journal volume. The unit is gigabytes.
◦
u is the usage rate of data in the master journal volume. The unit is percent.
◦
V is the data transfer speed between the primary and the secondary storage system. The
unit is MB/s (megabytes per second).
To find the usage rate of a journal volume, use the monitoring feature (see
).
The Universal Replicator for Mainframe SEQCHK status is indicated when a Universal Replicator
for Mainframe pair assigned to a consistency group with the System timer type accepts a
non-time-stamped update from the primary system. The SEQCHK status does not affect Universal
Replicator for Mainframe copy activities and will be removed when the next time-stamped
update is successfully copied to the secondary data volume. However, if a disaster or system
failure occurs before the next time-stamped update, the update sequence consistency between
the secondary data volume and other secondary data volumes in the consistency group is not
ensured. To ensure effective disaster recovery, you should detect and remove the source of
the SEQCHK status. The SEQCHK status can be caused by any of the following:
◦
An application may issue update I/Os bypassing the MVS standard I/O procedure.
◦
The I/O time-stamping function may not be active at the primary site.
◦
This Universal Replicator for Mainframe pair status describes:
–
Universal Replicator for Mainframe suspend types (see the next section),
–
Universal Replicator for Mainframe suspension condition (see
).
Table 5 Universal Replicator for Mainframe Data Volume Pair Status
Description
Pair Status
This volume is not currently assigned to a Universal Replicator for
Mainframe data volume pair. This volume does not belong in the
Simplex
journal group. When this volume is added to a Universal Replicator
38
About Universal Replicator for Mainframe Operations