466 Implementing the IBM Storwize V7000 with IBM Spectrum Virtualize V8.2.1
/SM590000FlashCopy licensing is based on the virtual capacity of the source volumes.
/SM590000Incremental FlashCopy copies all of the data when you first start FlashCopy, and then only 
the changes when you stop and start FlashCopy mapping again. Incremental FlashCopy 
can substantially reduce the time that is required to re-create an independent image.
/SM590000Reverse FlashCopy enables FlashCopy targets to become restore points for the source 
without breaking the FlashCopy relationship, and without having to wait for the original 
copy operation to complete.
/SM590000The size of the source and target volumes cannot be altered (increased or decreased) 
while a FlashCopy mapping is defined. 
IBM FlashCopy limitations for IBM Spectrum Virtualize V8.2 are listed in Table 11-8.
Table 11-8   FlashCopy limitations in V8.2
11.2  Managing FlashCopy by using the GUI
It is often easier to work with the FlashCopy function from the GUI if you have a reasonable 
number of host mappings. However, in enterprise data centers with many host mappings, use 
the CLI to run your FlashCopy commands.
11.2.1  FlashCopy presets
The IBM Spectrum Virtualize GUI interface provides three FlashCopy presets (Snapshot, 
Clone, and Backup) to simplify the more common FlashCopy operations.
Although these presets meet most FlashCopy requirements, they do not support all possible 
FlashCopy options. If more specialized options are required that are not supported by the 
presets, the options must be performed by using CLI commands. 
This section describes the preset options and their use cases.
Snapshot
This preset creates a copy-on-write point-in-time copy. The snapshot is not intended to be an 
independent copy. Instead, the copy is used to maintain a view of the production data at the 
time that the snapshot is created. Therefore, the snapshot holds only the data from regions of 
the production volume that changed since the snapshot was created. Because the snapshot 
preset uses thin provisioning, only the capacity that is required for the changes is used.
Snapshot uses the following preset parameters:
/SM590000Background copy: None
/SM590000Incremental: No
/SM590000Delete after completion: No
Property Maximum number
FlashCopy mappings per system 5000
FlashCopy targets per source 256
FlashCopy mappings per consistency group 512
FlashCopy consistency groups per system 255
Total FlashCopy volume capacity per I/O group 4096 TiB