text: Figure 11-60 FlashCopy mappings status and progress examples 
  
  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 a long time to 
  complete, depending on the size of the source volume and on the copyrate value. 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 450. 
  
  **11.2.17 Stopping FlashCopy mappings**
  
  <html>
          <head> <meta charset="UTF-8">
          <style>
          table, th, td {
              border: 1px solid black;
              font-size: 10px;
          }
          </style> </head>
          <body>
          <table frame="hsides" rules="groups" width="100%%">
              [html]<thead><tr><td>Important : Only FlashCopy mappings that do not belong to a consistency group can be</td></tr></thead><tbody><tr><td>stopped individually. If FlashCopy mappings are part of a consistency group. They can only</td></tr><tr><td>be stopped together by using the consistency group step command.</td></tr></tbody>
          </table> </body> </html>