Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.

SAP Sybase SQL Anywhere 16.0 » SQL Anywhere Server - Database Administration » High availability and read-only scale-out systems » Database mirroring » Application development considerations with database mirroring » Database mirroring modes


Mirror synchronization states

When a mirroring system is using synchronous mode, it can be in one of two states:

  • synchronizing   The mirror server is not connected or has not yet read all the primary server's log pages. This value is also returned if the synchronization mode is asynchronous

  • synchronized   The mirror server is connected and has all changes that have been committed on the primary server.

Once a partner server starts and determines that it is acting as the mirror, it first requests any log pages from the primary server that it does not already have. This may involve copying pages from log files other than the current active log on the primary server. As it receives these pages, the mirror applies the changes they contain to its copy of the database. Once all pages from the primary have been received, the primary and mirror are in a synchronized state. From that point onward, any changes committed on the primary must be sent to the mirror and acknowledged by the mirror.

In asynchronous and asyncfullpage mode, the mirror requests log pages as above; however, the two servers never enter a synchronized state. Once the mirror has requested all log pages available at the primary, the primary is notified that it must send any updated pages to the mirror.

In a read-only scale-out system, the synchronization state of copy nodes is always synchronizing.