
• The Fast Snap primary volume is used as a Continuous Access Journal S-VOL, and you are reaching
the Cnt Ac-J journal volume capacity limit.
• The Fast Snap license is invalid.
• The Fast Snap pair volumes are blocked.
• The current status of the Fast Snap pair does not allow the
raidcom modify snapshot -
snapshot_data create
or
raidcom modify snapshot -snapshot_data clone
command
to run on the pair.
• The current status of the Fast Snap, Business Copy, Continuous Access Synchronous, or Continuous
Access Journal pair does not allow the
raidcom modify snapshot -snapshot_data create
or
raidcom modify snapshot -snapshot_data clone
command to run on the pair.
After resolving these error conditions, make sure that all pairs in the consistency group are in "PAIR"
status before running the
raidcom modify snapshot -snapshot_data create
or
raidcom
modify snapshot -snapshot_data clone
command again. For details about Fast Snap pairs, see
on page 21.
Notes on storing snapshot data, and on cloning pairs
The
raidcom modify snapshot -snapshot_data create
or
raidcom modify snapshot -
snapshot_data clone
RAID Manager 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 Fast Snap
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 Fast Snap 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 Fast Snap pair. In
addition, snapshot data for a consistency group including the latter pair is being acquired.
Notes on storing snapshot data, and on cloning pairs
207
Summary of Contents for HPE XP7
Page 7: ...Documentation feedback 311 Contents 7...
Page 24: ...24 Overview of Fast Snap...
Page 109: ...2 In the Replication window click Edit Options Local Replication Configuring Fast Snap 109...
Page 186: ...186 Troubleshooting Fast Snap...
Page 187: ...Troubleshooting Fast Snap 187...
Page 214: ...The following table lists the items on this tab 214 Fast Snap GUI windows and wizards...