HP XP RAID Manager Software - Manual (Page 45)

Table 20 Troubleshooting for Snapshot (continued)
Causes and Solutions Problem
Causes: Pairsplit on a consistency group
terminates abnormally
•
All pairs in the consistency group are not in PAIR status. This may result in rejection of the
command rejection, Timeout (Error code: EX_EWSTOT), or suspension of the pair (Error code:
EX_EWSUSE).
•
During the operation, a pairresync or pairsplit-S operation is begun on another pair or pairs
in the consistency group. This may result in a timeout (Error code: EX_EWSTOT), or suspension
of the pair (Error code: EX_EWSUSE)
Solutions
• Make sure all pairs in the consistency group are in PAIR status an retry the operation.
•
Perform only one operation on the pairs in a consistency group at one time.
Error code EX_EWSTOT is generated, and the status of some Snapshot pairs in a consistency
group cannot be changed. Pairsplit on a consistency group
terminates abnormally when
Possible causes:
P-VOL shared with Continuous
Access Journal or Continuous
Access Synchronous
•
When a Cnt Ac-J S-VOL is used as Snapshot P-VOL, the capacity of the journal volumes for
this Cnt Ac-J pair is insufficient.
• The Snapshot license is invalid.
•
Snapshot pair volumes are blocked.
• The Snapshot pair is in a status in which the pairsplit command cannot be executed. See
“Statuses required for pair operations” (page 33) .
•
The Cnt Ac-S or Cnt Ac-J pair is in a status in which the pairsplit command cannot be executed.
Solution: After the cause or causes are corrected, change all status of the pairs to PAIR and
execute the pairsplit command again.
Causes: Restore pair operation
terminates abnormally
• The pair’s Snapshot data is being stored per consistency group.
•
The P-VOL is also a P-VOL in another Snapshot pair, and the Snapshot data in the second
pair is stored per consistency group.
Cause: You can create a consistency group with no Snapshot pairs. However, pairs created
with the At-Time Split option in this condition may be rejected. Creating consistency groups
when host server is down or
failed
Solution: Find the consistency group number in the Snapshot or Pair Operation window in Remote
Web Console, and create a pair specifying the consistency group number intentionally.
Recovering from failure during pairresync -restore
If a failure occurs during pair restoration and pair status changes to PSUE, data in the P-VOL cannot
be insured. You can either delete the pair and create a new pair; or resynchronize the pair to
establish consistency in the P-VOL, then overwrite the P-VOL with backup data.
Recovering a terminated HP-UX host server
An error may occur and the HP-UX host server terminates if a volume that has already been
recognized by the host server is later used as a V-VOL in a paircreate operation. Pairs should be
created prior to issuing the command to recognize a device. To recover, proceed as follows:
1.
Force the command process and its parent process to terminate.
2. Create a Snapshot pair. Make sure the emulation type is “0” (OPEN-0V) for both the V-VOL
volume and the VDEV for the V-VOL group.
3. Split the pair, storing Snapshot data in the pool.
4. Execute the command to recognize the device.
General troubleshooting 45