GLYPH<SM590000> A volume cannot be configured for a cloud snapshot if any of the following conditions are valid: 

– The volume is part of a remote copy relationship (Metro Mirror, Global Mirror, active-active) master, auxiliary, or change volume. This configuration prevents the cloud snapshot from being used with HyperSwap volumes. 

– The volume is a VMware vSphere Virtual Volumes volume, including IBM FlashCopy owned volumes that are used internally for Virtual Volumes restoration functions. 

– The volume is a f ile system volume. 

– The volume is associated with any user-owned FlashCopy maps. 

– The volume is a mirrored volume with copies in different storage pools. 

– The volume is being migrated between storage pools. 

GLYPH<SM590000> A volume cannot be enabled for cloud snapshots if the cloud storage is set to import mode. 

GLYPH<SM590000> A volume cannot be enabled for cloud snapshots if the maximum number of cloud volumes exists. The maximum number of cloud volumes on the system is 1024. If the system exceeds this limit, you can disable cloud snapshots on an existing cloud volume and delete its associated snapshots from the cloud storage to accommodate snapshots on new cloud volumes. 

GLYPH<SM590000> A volume cannot be used for a restore operation if it meets any of the following criteria: 

– A Virtual Volume, including FlashCopy volu mes that are used internally for Virtual Volumes restoration functions. 

– Part of a remote copy relationship (Metro Mirror, Global Mirror, active-active) master, auxiliary, or change volume. 

GLYPH<SM590000> A volume that is configured for backup or is being used for restoration cannot be moved between I/O groups. 

GLYPH<SM590000> Only one operation (cloud snapshot, restore, or snapshot deletion) is allowed at a time on a cloud volume. 

GLYPH<SM590000> Cloud volume traffic is allowed only through management interfaces (1 G or 10 G). 

## 5.7.2 Restore to the production volume 

The snapshot version is restored to the production volume, which is the original volume from which the snapshots were created. After the restore operation completes, the snapshot version completely replaces the current data that exists on production volume. During the restore operation, the production volume goes offline until it completes. If you do not want to have the production volume offline for the restore, you can restore a cloud snapshot to a new volume. The production volume remains online and host operations are not disrupted. 

## 5.7.3 Restore to a new volume 

When the snapshot version is restored to a new volume, you can use the restored data independently of the original volume from which the snapshot was created. If the new volume exists on the system, then the restore operation uses the unique identifier (UID) of the new volume. If the new volume does not exist on the system, you need to choose whether to use the UID from the original volume or create a new UID. If you plan on using the new volume on the same system, use the UID that is associated with the snapshot version that is being restored. 

