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 » SQL Anywhere Veritas Cluster Server agents » SAServer agent configuration

 

Setting up a database server for failover using the SAServer agent

You can set up a database server to failover to another database server by using the Veritas Cluster Server.

Prérequis

Your systems must be set up as follows to use the SQL Anywhere Veritas Cluster Server agents:

  • You must use Veritas Cluster Server 4.1 or later.

  • SQL Anywhere must be installed identically on each system node within the cluster.

  • Database files must be stored on a shared storage device that is accessible to all systems within the cluster.

  • The utility database password must be the same for all systems within the cluster.

    The SADatabase agent uses the utility database to start and stop specific database files. All systems participating in the cluster must have the same utility database password. You can set the utility database password by specifying the -su server option when starting the database server.

  • On Unix, the VCS agent is installed in $SQLANY16/vcsagent/saserver.

When stopping a network server, you must supply a connection string with a user ID that has permissions to stop the server. By default, the SERVER OPERATOR system privilege is required to stop the network server. You can use the -gk server command-line option to change the default behavior.

 Task
  1. Start the Veritas Cluster Server Manager and enter your user name and password to connect.

  2. Add SAServer as a resource to a service group:

    1. Click Edit » Add » Resource.

    2. In the Resource Type list, click SAServer.

      On Windows, if SAServer does not appear in the Resource Type list under Windows, you may have to add the SAServer.xml file to the %VCS_ROOT%\cluster manager\attrpool\Win2K\400 and restart the cluster services.

    3. In the Resource Name field, type a name.

    4. Add the following attribute values to the following attributes:

      • cmdStart   dbsrv16 -x tcpip database-file-on-shared-disk -n server-name

      • cmdMonitor   dbping -c "Server=server-name"

      • cmdStop   dbstop -c user-id,password -y

    5. Click Enabled.

      This indicates that the resource is ready to be used.

    6. Click OK.

  3. Ensure that the resource dependencies are configured correctly. There are other resources that must be started and grouped together before SAServer can be started, such as the shared disk resources and the IP address resources.

  4. Right-click the service group and click Online » node-name, where node-name is the name of the computer in the cluster on which you want the resource to run.

Résultat

The service group is now online.

 See also