Mirror Replication Agent for ASE 15.1 provides support for ASE Cluster Edition (CE).
In an ASE CE replication environment, the Mirror Replication Agent must be able to connect to any node in the cluster in the event that a node fails or otherwise becomes unavailable. To support the configuration of multiple node locations, Mirror Replication Agent supports connectivity to all possible ASE CE database instances using the Sybase open-client/open-server interfaces (UNIX) or sql.ini (Windows) file. Instead of configuring individual host, port, and instance names for all nodes, the Mirror Replication Agent requires only the location of the interfaces or sql.ini file, the ASE CE server name, and the primary database name. The interfaces or sql.ini file specified should contain an entry that includes the address for each node in the database cluster.
For example, if the following entry exists in the interfaces file for a two-node cluster, Mirror Replication Agent can be instructed to use that entry by providing the interfaces file location to the pds_interfaces_file configuration property and specifying “clustA” as the value for the pds_server_name configuration property:
clustA
query tcp ether suse9364asece1.sybase.com 4311
query tcp ether suse9364asece2.sybase.com 4312
See the Mirror Replication Agent Reference Manual for details about the pds_interfaces_file and pds_server_name parameters.
Mirror Replication Agent must have read access to the interfaces or sql.ini file,
which you should copy from the machine on which the primary database
is running to the machine on which Mirror Replication Agent is running.
On initialization, the Mirror Replication Agent automatically determines that the primary database is a cluster database so, besides database connectivity, Mirror Replication Agent does not require any other unique configuration to support ASE CE database replication.
If the ASE CE instance to which Mirror Replication Agent is connected fails for any reason, Mirror Replication Agent attempts to reconnect to any surviving instance, choosing from the list of instances defined in the interfaces or sql.ini file entry Mirror Replication Agent is configured to use. No manual intervention or configuration is required. If none of the instances are available, Mirror Replication Agent reports a warning and continues replication processing.
