Configure for asymmetric configuration

Configure the primary companion for asymmetric configuration. Issue the following from the secondary companion:

sp_companion "primary_server_name", configure, with_proxydb, login_name, password

where:

This example configures an Adaptive Server named PERSONNEL1 as a secondary companion:

sp_companion "PERSONNEL1", configure, with_proxydb, sa, Odd2Think
Server 'MONEY1' is alive and cluster configured.
Step: Access verified from Server:'MONEY1' to Server:'PERSONNEL1'
Server 'PERSONNEL1' 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

If user databases already exist while you are using sp_companion, you see messages similar to these:

Step: Created proxy database ‘pubs2’
 Step: Proxy status for database has been set. Please Checkpoint the database 'pubs2'
 Step: Server configured in normal companion mode”
 Starting companion watch thread

See “Asymmetric companion configuration” for more information about asymmetric configuration.