Support for replication

The Cluster Edition supports replication using Replication Server and the RepAgent thread. A clustered database can be a source or a destination in a Sybase clustered system. You can perform all of the tasks, such as configuring RepAgent or marking tables for replication, from any instance in the cluster. Replication status is coherent across the entire cluster.

Configuring the RepAgent

When you configure a primary database in a clustered system, the server name you specify should be the cluster name. You can display the cluster name using select @@servername.

The syntax for sp_config_rep_agent does not require a cluster or instance name. By default, both the Cluster Edition and the nonclustered Adaptive Server edition assume the value of select @@servername. In the Cluster Edition, this statement returns the current cluster name. For example:

1> select @@servername
2> go

---------------------------
MYCLUSTER

Starting the RepAgent

By default, RepAgent starts on the coordinator.

However, you can configure RepAgent to start on any instance in the cluster. For example, to configure RepAgent on the primary database pdb to always start on the “ase2” instance, enter:

sp_config_rep_agent pdb, "cluster instance name", "ase2"

After configuration, you must restart RepAgent using sp_start_rep_agent for the new configuration to take effect.

To return to the default behavior with RepAgent always starting on the coordinator, enter:

sp_config_rep_agent pdb, "cluster instance name", "coordinator"

When an instance starts on its node, it checks if databases are configured to start on its node. If yes, and if the database is marked to start automatically, the RepAgent starts.

When the coordinator starts, it starts all RepAgents not configured to start on a specific instance. If the coordinator fails, or is stopped with a graceful shutdown, a RepAgent starts on the new coordinator.

If a RepAgent is configured to start on a specific instance other than the coordinator, and this instance is shutdown or fails, the RepAgent starts on the coordinator.

NoteThe Cluster Edition does not support Adaptive Server Enterprise Replicator, which requires the unsupported dbcc logtransfer interface.