A summery about VVR replication mode.

cuhutai2494

于 2009-02-12 15:42:01 发布

阅读量167

点赞数

本文详细对比了VVR同步与异步模式的工作原理。异步模式下，数据库事务提交后，VVR立即记录并发送日志，但存在潜在的数据丢失风险；同步模式则确保远程站点的日志同步完成后再提交事务，避免了数据丢失。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

By my understanding the main difference between Sync and Async for VVR is how VVR writes VVR log and ship it to DR side. [@more@]

Async mode,

1> Oracle messages OS to request IO operations to write oracle redo buffer into a certain group of log files when a client process commits a transaction.

2> Oracle writes redo buffer into a certain group of log files.

3> Oracle completes the transaction and won’t wait for VVR.

4> VVR get the message from OS immediately and writes the log entries about Changed OS blocks into local VVR log and then ship the VVR log to DR side immediately.

5> VVR applies VVR logs transferred from primary side catch up with the primary side at OS level – OS blocks synchronize, which doesn’t affect the performance at primary side at all.

6> The potential data loss is the delay of VVR log transfer over LAN when the primary crash.

Sync mode,

1> Oracle messages OS to request IO operations to write oracle redo buffer into a certain group of log files when a client process commits a transaction.

2> Oracle writes redo buffer into a certain group of log files while VVR writes VVR log at remote side over LAN and applies the log to catch up the primary.

3> Oracle can’t finish the transaction until VVR writes VVR log at remote side over LAN and applies the log to catch up the primary as well as for sure Oracle writes redo buffer into a certain group of log files.

4> There will be no potential data loss after failover to DR.

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/76065/viewspace-1017242/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/76065/viewspace-1017242/