Table of Contents
Advertisement
snapshot -snapshot_data create or raidcom modify snapshot -
snapshot_data clone command again. For details about Thin Image pairs,
see
How Thin Image works on page
Notes on storing snapshot data, and on cloning pairs
There are some situations in which storing snapshot data or cloning pairs
might end abnormally.
The raidcom modify snapshot -snapshot_data create or raidcom modify
snapshot -snapshot_data clone CCI command might terminate
abnormally, as shown below, if the consistency group includes a pair in a
status other than "PAIR."
• The command is rejected.
• Timeout occurs with the error code EX_EWSTOT.
• The pair is suspended with the error code EX_EWSUSE.
If you perform an operation other than pairsplit (for example, deletion of
snapshot data or a Thin Image pair) on a pair in the consistency group while
the raidcom modify snapshot -snapshot_data create or raidcom modify
snapshot -snapshot_data clone command is running, consistency of
snapshot data to be stored or the S-VOL in which pairs are cloned cannot be
maintained. Therefore, the raidcom modify snapshot -snapshot_data
create or raidcom modify snapshot -snapshot_data clone command
might end abnormally as shown below.
• Timeout might occur with the error code EX_EWSTOT.
• The pair might be suspended with the error code EX_EWSUSE.
Restoring a Thin Image pair might end abnormally in either of the following
conditions.
• Snapshot data for a consistency group including the pair is being acquired.
• The primary volume of the pair is also used as the primary volume of
another Thin Image pair. In addition, snapshot data for a consistency
group including the latter pair is being acquired.
Hitachi Thin Image User Guide for Hitachi Virtual Storage Platform G Series and F Series
CCI command reference for Thin Image
26.
223
- Quick Links:
- Table of Contents
- About Thin Image
Hide quick links:
Advertisement
Table of Contents
Troubleshooting
