Configuring for symmetric configuration

After you configure the companions for asymmetric failover, you can configure them for symmetric configuration. In a symmetric configuration, both servers act as primary and secondary companions. See Figure 3-2 for a description of symmetric configuration.

Before you configure for a symmetric set up, you must first use the scswitch utility to disable the monitoring of the primary and secondary resources:

scswitch -n -M -j primary_resource
scswitch -n -M -j secondary_resource

Issue sp_companion from the secondary companion to configure it for symmetric configuration. Use the same syntax as for asymmetric configuration. See “Configuring for asymmetric configuration”” for a description of the syntax for sp_companion.

The following example adds an Adaptive Server named PERSONNEL1 as the primary companion to the Adaptive Server named MONEY1.

sp_companion 'PERSONNEL1', configure, with_proxydb, sa, Think2Odd
Server 'PERSONNEL1' is alive and cluster configured.
Step: Access verified from Server:'MONEY1' to Server:'PERSONNEL1'
Server 'MONEY1' is alive and cluster configured.
Step: Access verified from Server:'PERSONNEL1' to Server:'MONEY1'
(1 row affected)
(1 row affected)
(1 row affected)
(1 row affected)
(1 row affected)
(1 row affected)
.....
Step: Companion servers configuration check succeeded
Step: Server handshake succeeded
Step: Master device accessible from companion
Step: Added the servers 'MONEY1' and 'PERSONNEL1' for cluster config
Step: Server configuration initialization succeeded
Step: Synchronizing server logins from companion server
Step: Synchronizing remoteserver from companion server
Step: Synchronizing roles from companion server
Step: Synchronizing server-wide privs from companion server
Step: User information syncup succeeded
Step: Server configured in normal companion mode

Change the Nodelist property of the secondary resource group to include both nodes:

scrgadm -c -g secondary_group -y NodeList=secondary_node,primary_node

The following example changes the Nodelist property of the resource group rg_PERSONNEL1 which contains the Adaptive Server PERSONNEL1:

scrgadm -c -g rg_PERSONNEL1 -y NodeList=node2,node1

Use the scswitch utility to enable the monitoring of the primary and secondary resources:

scswitch -e -M -j primary_resource
scswitch -e -M -j secondary_resource