text: Since V7.8, it is possible to create a FlashCopy mapping (Change Volume) for a remote copy 
  target volume to maintain a consistent image of the secondary volume. The system 
  recognizes it as a*Consistency Protection*and a link failure or an offline secondary volume 
  event is handled differently now. 
  
  <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>When Consistency Protection is configured, the relationship between the primary and</td></tr></thead><tbody><tr><td>Poul / Number of the study I living alpha - always aloned although allone - blood although session - basis - alpha - alpha - alpha - alpha - alpha - alcohol</td></tr><tr><td>secondary change volume to automatically copy the previous consistent state of the</td></tr><tr><td>secondary volume. The relationship automatically moves to the consistent copying status as</td></tr><tr><td>the system resynchronizes and protects the consistency of the data.</td></tr><tr></tr></tbody>
          </table> </body> </html>