text: <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>• The application might fail to detect that the data is corrupted and return erroneous data.</td></tr></thead><tbody><tr><td>• The application might work without a problem.</td></tr><tr><td>Because of the risk of data corruption, and in particular undetected data corruption, MM / GM strongly enforces the concept of consistency and prohibits access to inconsistent data.</td></tr><tr><td>Consistency as a concept can be applied to a simple relationship or a set of relationships in a Consistency Strup, When othering is a concept that an application can maintain across several disks that are accessed through multiple systemb</td></tr><tr><td>When you are deciding how to use Consistency Groups, the administrator must consider the scope of an application ’ s data and consider all of the interdependent systems that communicate and exchange information.</td></tr><tr><td>If two programs or systems communicate and store details as a result of the information that is exchanged, either of the following actions might occur :</td></tr><tr><td>• All of the data that is accessed by the group of systems must be placed into a single Consistency Group.</td></tr><tr><td>• The systems must be recovered independently ( each within its own Consistency Group ). Then, each system must perform recovery with the other applications to become consistent with them.</td></tr><tr><td>Consistent versus synchronized</td></tr><tr><td>A copy that is consistent and up - to - date is described as rn - snickcyal, lin a synchronized relationship, the master and susiliary volumes differ only in regions where writes are outstanding from the host.</td></tr><tr><td>Consistency does not mean that the data is up - to - date. A cogy can be consistent and yet contain data that was frozen at a point in the past. Wite VO might continue to a master but not be copied to the ausiliary. This state anise when it becomes it</td></tr><tr><td>When communication is lost for an extended period and Consistency Protection was not enabled, MMCEM tocks the changes that occurred on the master, but not the order or the details of such changes ( when data ). When communication is restore</td></tr><tr><td>Note : MM / GM relationships with Consistency Protection enabled use a point - in - time copy mechanism ( FastCays ) to keep a consistent copy of the auxiliary. The relationships site / in a consistent state, although not synchronized, eveni</td></tr><tr></tr></tbody>
          </table> </body> </html>