Moving the arbiter server

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

Prerequisites

You must have the MANAGE ANY MIRROR SERVER system privilege.

Task

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

dbsrv16 -n demo_arbiter2 -x "tcpip(port=6873)" -xf c:\arbiter2\arbiter2.state -xa "AUTH=abc;DBN=mirror_demo" -su sql

Connect to the primary server and alter the arbiter mirror server definition for the mirroring system so that the connection_string is for the new arbiter server.

For example, execute the following statement to change the arbiter server definition to that of the new server.

ALTER MIRROR SERVER demo_arbiter 
AS ARBITER 
connection_string='SERVER=demo_arbiter2;HOST=localhost:6873';

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

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

Results

The arbiter server is moved to the new server.

Next

Ping the ArbiterState database property of the mirroring system to ensure that the new arbiter server is connected to the mirroring system. For example, run the following command:

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

The value for the ArbiterState is connected:

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

Moving the arbiter server

Task

See also