Symantec Replicator Option ( v. 6.1 ) - license
Mfg # 4M1OUKF0-ZZZAS
CDW # 3219105
| UNSPSC 43232804
Software Details
- ( v. 6.1 )
- 1 server
- Tier K
- level S ( 1+ )
- license
- EDU
- Symantec Buying Programs : Academic
- UNIX
Know your gear
In synchronous mode, all data writes are first posted to the SRL and then sent to the secondary location (s). The posting of the data to the actual data volumes happens in this time period also. When the secondary location (s) receives the data write and acknowledgment is sent back to the primary location, then the application acknowledges the data write to be complete. Therefore, synchronous replication should be used in environments that cannot afford any data loss and can afford some application performance impact. Overall performance in synchronous mode is governed by the amount of time that it takes to write to the SRL plus the round-trip time to send data to the secondary and receive acknowledgment.
The secondary acknowledges receipt as soon as the full write transaction (as sent by the application on the primary) is received into Volume Replicator kernel memory space. This removes actual writing to the secondary data volumes from the application latency. The primary tracks these writes in its SRL until a second acknowledgment is received from the secondary, signaling that the data has been written to physical storage. Both acknowledgments have an associated timeout, so if a packet is not acknowledged, it will be re-sent.
To maximize performance, Volume Replicator only waits for data to be received. Not waiting for data to be written at the secondary improves application performance. But it tracks all acknowledged, uncommitted transactions and can replay any necessary transactions if the secondary were to crash prior to actually writing its data to the physical storage. Synchronous mode has two possible RLINK settings: "fail" and "override". These settings deal with the behavior of Volume Replicator when the network connection is lost to a secondary site.
The secondary acknowledges receipt as soon as the full write transaction (as sent by the application on the primary) is received into Volume Replicator kernel memory space. This removes actual writing to the secondary data volumes from the application latency. The primary tracks these writes in its SRL until a second acknowledgment is received from the secondary, signaling that the data has been written to physical storage. Both acknowledgments have an associated timeout, so if a packet is not acknowledged, it will be re-sent.
To maximize performance, Volume Replicator only waits for data to be received. Not waiting for data to be written at the secondary improves application performance. But it tracks all acknowledged, uncommitted transactions and can replay any necessary transactions if the secondary were to crash prior to actually writing its data to the physical storage. Synchronous mode has two possible RLINK settings: "fail" and "override". These settings deal with the behavior of Volume Replicator when the network connection is lost to a secondary site.