You can check the FlashCopy state and the progress of the mappings in the Status and  Progress columns of the table, as shown in Figure 11-60.  FlashCopy Snapshots are dependent on the source volume and should be in a “copying”  state if the mapping is started. FlashCopy clones and the first occurrence of FlashCopy backup can take some time to  complete, depending on the copyrate value and the size of the source volume. The next  occurrences of FlashCopy backups are faster because only the changes that were made  during two occurrences are copied. For more information about FlashCopy starting operations and states, see 11.1.10, “Starting  FlashCopy mappings and Consistency Groups” on page 475. Important:  Only FlashCopy mappings that do not belong to a consistency group can be  stopped individually. If FlashCopy mappings are part of a consistency group, they can only  be stopped all together by using the consistency group  stop  command. The only reason to stop a FlashCopy mapping is for incremental FlashCopy. When the first  occurrence of an incremental FlashCopy is started, a full copy of the source volume is made.  When 100% of the source volume is copied, the FlashCopy mapping does not stop  automatically and a manual stop can be performed. The target volume is available for read  and write operations, during the copy, and after the mapping is stopped. In any other case, stopping a FlashCopy mapping interrupts the copy and resets the bitmap  table. Because only part of the data from the source volume was copied, the copied grains  might be meaningless without the remaining grains. Therefore, the target volumes are placed  offline and are unusable, as shown in Figure 11-61 on page 523. 11.2.17 Stopping FlashCopy mappings Figure 11-59 Starting FlashCopy mappings Figure 11-60 FlashCopy mappings status and progress examples 522  Implementing the IBM System Storage SAN Volume Controller with IBM Spectrum Virtualize V8.2.1