Restoring a Thin Image pair overwrites the existing P-VOL data with the differential data on the S-VOL.
Restoration of a Thin Image pair may end abnormally in either of the following conditions:
- You are storing snapshot data for a consistency group that already includes the pair.
- You are using the P-VOL of the pair as the P-VOL of another Thin Image pair and you are storing snapshot data for a consistency group including the latter pair.
For Thin Image pairs where the cascade attribute is enabled, the information displayed in Synchronization Rate (%) of the View Pair Synchronization Rate window, or the information displayed by the raidcom get snapshot command varies depending on the pair status. For details, see View Pair Synchronization Rate window.
For more information about restoring suspended Thin Image pairs, see Restoring suspended Thin Image pairs.
The amount of time required for restoration depends on the following, even if the pair synchronization rate is 100 percent:
- The amount of capacity the pool is using.
- The number of pairs being resynchronized concurrently.
For Thin Image pairs where the cascade attribute is enabled, the information displayed in Synchronization Rate (%) of the View Pair Synchronization Rate window, or the information displayed by the raidcom get snapshot command varies depending on the pair status. For details, see View Pair Synchronization Rate window.
For more information about monitoring the pair synchronization rates, see Viewing pair synchronization rates.
If you use CCI commands, see Pair tasks using CCI or Device Manager - Storage Navigator.
- You must have the Storage Administrator (Local Copy) role.
- The Thin Image pair must be split ("PSUS" status).