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


Tutorial: Moving the arbiter server

Move an arbiter server without stopping the mirroring system, by creating new server and changing the arbiter server definitions to use the new arbiter server.


This tutorial relies on the database mirroring system described in Tutorial: Creating a database mirroring system.

You must have the MANAGE ANY MIRROR SERVER and SERVER OPERATOR system privileges.

Context and remarks

In this tutorial, all the database servers are running on the same computer. However, each database server must be installed on a separate computer in a production environment.

If this tutorial is used with database servers running on different computers, references to localhost in the connection strings must be changed to the actual computer names.

  1. Start the server to become the arbiter with the -su, -xa, and -xf options. For example:

    mkdir arbiter2
    dbsrv16 -n demo_arbiter2 -x "tcpip(port=6873)" -xf c:\arbiter2\arbiter2.state -xa "AUTH=abc;DBN=mirror_demo" -su sql
    Option Description
    -su password for the utility database.
    -xa database name and authentication string of the arbiter server.
    -xf location of the state information file for the mirroring system.
  2. Connect to the primary server and alter the arbiter server definition for the mirroring system.

    1. Run the following command to connect to the primary server.

      dbisql -c "UID=DBA;PWD=sql;SERVER=mirror_demo_primary;HOST=localhost:6871,localhost:6872"
    2. Execute the following command to change the arbiter server definition to that of the new server.

      ALTER MIRROR SERVER demo_arbiter

    The primary and mirror servers disconnect from the arbiter server and connect to the new arbiter server.

  3. Wait a few seconds, and then stop the old arbiter server.

    dbstop -y -c "UID=DBA;PWD=sql;SERVER=demo_arbiter;HOST=localhost:6870;DBN=utility_db"
  4. Ping the ArbiterState database property of the mirroring system to ensure that the new arbiter server is connected to the mirroring system. Run the following command:

    dbping -c "UID=DBA;PWD=sql;SERVER=mirror_demo_primary" -pd ArbiterState

    The value for the ArbiterState property is connected:

        SQL Anywhere Server Ping Utility Version
        Type       Property                  Value
        ---------  ----------------          ------------------------------
        Database   ArbiterState              connected


The arbiter server is moved to the new server.