 | ||
| Mode of replication - synchronous attribute | ||
|---|---|---|
| Prev | Understanding replication settings for a Secondary | Next |
| ||
| Mode of replication - synchronous attribute | ||
|---|---|---|
| Prev | Understanding replication settings for a Secondary | Next |
Volume Replicator replicates in two modes: synchronous and asynchronous. The decision to use synchronous or asynchronous mode must be made with an understanding of the effects of this choice on the replication process and the application performance. You can set up Volume Replicator to replicate to a Secondary in synchronous override or asynchronous mode by setting the synchronous attribute of the Secondary to override, or off respectively.
Note: |
While you set the mode of replication from the GUI, the synchronous override is the default mode of replication. |
The following table summarizes the effect of RLINK on modes of replication.
Table: Effect of RLINK state on modes of replication
These terms have been explained as follows:
synchronous=off
Specifying the attribute value as off sets the replication mode to asynchronous.
synchronous=override
Specifying the attribute value as override sets the replication mode to synchronous override. During normal operation, Volume Replicator replicates in synchronous mode, but if the RLINK is disconnected, Volume Replicator switches temporarily to asynchronous mode and continues to receive writes from the application and logs them in the Replicator Log. After the connection is restored and the RLINK is up-to-date, the RLINK automatically switches back to synchronous mode. Most system administrators set synchronous=override.
synchronous=fail
Specifying the attribute value as fail sets the replication mode to synchronous. During normal operation, Volume Replicator replicates in synchronous mode, but if the RLINK is disconnected, Volume Replicator fails incoming writes to the Primary.