Table 11-7 FlashCopy and remote copy interaction Component Remote copy primary site Remote copy secondary site  FlashCopy Source Supported Supported latency: When the  FlashCopy relationship is in the  preparing  and  prepared  states,  the cache at the remote copy  secondary site operates in  write-through mode. This process adds latency to  the latent remote copy  relationship.  FlashCopy Target This is a supported combination  and has the following  restrictions: GLYPH<SM590000> Issuing a  stop -force  might cause the remote  copy relationship to be fully  resynchronized. GLYPH<SM590000> Code level must be 6.2. x  or  later. GLYPH<SM590000> I/O Group must be the  same. This is a supported combination  with the major restriction that  the FlashCopy mapping cannot  be  copying ,  stopping , or  suspended . Otherwise, the  restrictions are the same as at  the remote copy primary site. 11.1.20 FlashCopy attributes and limitations The FlashCopy function in IBM Spectrum Virtualize features the following attributes: GLYPH<SM590000> The target is the time-zero copy of the source, which is known as  FlashCopy mapping  target . GLYPH<SM590000> FlashCopy produces an exact copy of the source volume, including any metadata that was  written by the host operating system, Logical Volume Manager (LVM), and applications.  GLYPH<SM590000> The source volume and target volume are available (almost) immediately following the  FlashCopy operation. GLYPH<SM590000> The source and target volumes must be the same “virtual” size. GLYPH<SM590000> The source and target volumes must be on the same Storwize V7000 system. GLYPH<SM590000> The source and target volumes do not need to be in the same I/O Group or storage pool. GLYPH<SM590000> The storage pool extent sizes can differ between the source and target. GLYPH<SM590000> The target volumes can be the source volumes for other FlashCopy mappings ( cascaded  FlashCopy ). But a target volume can only have one source copy. GLYPH<SM590000> Consistency groups are supported to enable FlashCopy across multiple volumes at the  same time. GLYPH<SM590000> The target volume can be updated independently of the source volume. GLYPH<SM590000> Bitmaps that are governing I/O redirection (I/O indirection layer) are maintained in both  nodes of the Storwize V7000 I/O Group to prevent a single point of failure. GLYPH<SM590000> FlashCopy mapping and Consistency Groups can be automatically withdrawn after the  completion of the background copy. GLYPH<SM590000> Thin-provisioned FlashCopy (or Snapshot in the graphical user interface (GUI) use disk  space only when updates are made to the source or target data, and not for the entire  capacity of a volume copy. Chapter 11. Advanced Copy Services  465