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

SQL Anywhere 12.0.1 » SQL Anywhere Server - Database Administration » Database maintenance » SQL Anywhere high availability » Database mirroring system setup


Database mirroring scenarios

The following scenarios help you understand what happens when a server becomes unavailable in a mirroring system. The scenarios use the following database mirroring configuration, which consists of Server 1, Server 2, and an arbiter server running in synchronous mode:

An example database mirroring system, consisting of Server 1, Server 2, and an arbiter server.

At any time, you can use the MirrorState, PartnerState, and ArbiterState database properties to determine the status of the database servers in the mirroring system. See MirrorState database property, PartnerState database property, and ArbiterState database property.

Communications between the primary, mirror, and arbiter servers are checked regularly in a mirroring system. A interruption in the communication between the three servers can be caused by one or more server becoming unavailable and/or an outage of the network between the servers.

 Scenario 1: Primary server becomes unavailable
 Scenario 2: Primary server becomes unavailable and then restarts
 Scenario 3: Mirror server becomes unavailable
 Scenario 4: Mirror server becomes unavailable and then restarts
 Scenario 5: Arbiter becomes unavailable
 Scenario 6: Arbiter restarts