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>relationship can be lool. Alternatively, the fabric connection between the two systems might fail, which leaves the two systems that are running but cannot communicate with each other.</td><td>When the two systems can communicate, the oystems and the relationships that spans them are described as a vonv - rul. When they cannot communicate, the systems and the relationships spanning them are described as alivoxecise.</td></tr></thead><tbody><tr><td>In this state, both systems are left with fogmented relationships and are limited regarding the configuration commands that care be performed. The discomected relationships are portrayed as having a changed state. The new states descr</td><td>When the systems can communicate again, the relationships are recommected. MM / CM uutomatically reconclear the heart fragments, considering any configuration or other event that occurred while the relationship was discomected, Ase</td></tr><tr><td>Relationships that are configured between volumes in the same BM Stonwize V7000 system ( intracluster ) are never described as being in a discornected state.</td><td>Consistent versus inconsistent</td></tr><tr><td>Relationships that contain volumes that are operating as secondar - test care be described as being consistent or inconsistent. Consistency Groups that contain relationships can also be described as being consistent or inconsistenth</td><td>An auxillary volume is described as consistent if it contains data that can be read by a host system from the master if power failed at an imaginary point while I / O was in progress, and power was later restored. This imaginary point is defined</td></tr><tr><td>The requirements for consistency are expressed regarding activity at the master up to the recovery point. The auxiliary volume contains the data from all of the writes to the master for which the host received successful completion and th</td><td>Consider writes for which the host did not receive a successful completion ( that is, it received basel completion or no completion at all ), if the host then performed a nead from the master of that data that refurned successful completion a</td></tr><tr></tr><tr></tr><tr></tr><tr></tr><tr></tr></tbody>
          </table> </body> </html>