Notes on using Thin Image primary volumes as TrueCopy, ShadowImage, or Universal Replicator pair volumes

The raidcom modify snapshot -snapshot_data create or raidcom modify snapshot -snapshot_data clone CCI command might return the error code EX_EWSTOT (timeout) and terminate abnormally when the status of a pair in a Thin Image consistency group cannot be changed.

Following are possible reasons why the pair status cannot be changed:

• The Thin Image primary volume is used as a Universal Replicator S-VOL, and you are reaching the UR journal volume capacity limit.
• The Thin Image license is invalid.
• The Thin Image pair volumes are blocked.
• The current status of the Thin Image 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 Thin Image, ShadowImage, TrueCopy, or Universal Replicator 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 Thin Image pairs, see How Thin Image works.

Parent Topic

• Troubleshooting with Command Control Interface

  To identify the cause of errors that occur when you run CCI commands, refer to the log displayed in the CCI window or the CCI operation log file.

Child Topics

• Notes on storing snapshot data, and on cloning pairs

  There are some situations in which storing snapshot data or cloning pairs might end abnormally.