496 Implementing the IBM Storwize V7000 with IBM Spectrum Virtualize V8.2.1
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.
Figure 11-61   Showing target volumes state and FlashCopy mappings status
To stop one or multiple FlashCopy mappings that do not belong to a consistency group, 
complete the following steps:
1. Open the FlashCopy Consistency Gr oups, or FlashCopy Mappings window.
2. Right-click the FlashCopy mappings that you want to start and select Stop, as shown in 
Figure 11-62.
Figure 11-62   Stopping FlashCopy mappings
11.2.18  Memory allocation for FlashCopy
Copy Services features require that small amounts of volume cache be converted from cache 
memory into bitmap memory to allow the functions to operate at an I/O group level. If you do 
not have enough bitmap space allocated when you try to use one of the functions, you cannot 
complete the configuration. The total memory that can be dedicated to these functions is not 
defined by the physical memory in the system. The memory is constrained by the software 
functions that use the memory.
For every FlashCopy mapping that is created on an IBM Spectrum Virtualize system, a 
bitmap table is created to track the copied grains. By default, the system allocates 20 MiB of 
memory for a minimum of 10 TiB of FlashCopy source volume capacity and 5 TiB of 
incremental FlashCopy source volume capacity.
Note: FlashCopy mappings can be in a stopping state for a long time if you created 
dependencies between several targets. It is in a cleaning mode. For more information 
about dependencies and stopping process, see “Stopping process in a Multiple Target 
FlashCopy - Cleaning Mode” on page 456.