When copying a volume using both an external volume and a DP-VOL, verify that the copy target pool has free space exceeding the defined capacity of the copy source volume. For example, when copying a volume with a defined capacity of 100 GB, the target pool must have at least 100 GB of free space, even if the used capacity of the volume is 30 GB. This is because the page assignment information on the external volume is not taken over by the local storage system. If an external volume is a DP-VOL in Dynamic Tiering or active flash, the information about the I/O load on the page and the tier configuration on the external volume are not also taken over by the copy target volume.
Case 1 shows that a mapped external volume on the external storage system is copied to an S-VOL on the local storage system. When A is copied to B, a pool on B must have free space exceeding the defined capacity of A.
- A indicates an external volume mapped to the local storage system.
- B indicates a volume on the local storage system.
Case 2 shows that a P-VOL on the local storage system is copied to a mapped external volume on the external storage system. When B is copied to A, a pool on A must have free space exceeding the defined capacity of B.
- A indicates an external volume mapped to the local storage system.
- B indicates a volume on the local storage system.
These restrictions apply to the following software:
- TrueCopy
- TrueCopy for Mainframe
- Global-active device
- Universal Replicator
- Universal Replicator for Mainframe
- ShadowImage for Mainframe
- ShadowImage
- Volume Migration
- Thin Image