Configure the primary companion for asymmetric configuration. From the secondary companion, enter:
sp_companion "primary_server_name", configure, with_proxydb, login_name, password, cluster_login, cluster_login_password
Where:
primary_server_name is the name of the primary Adaptive Server as defined in the sql.ini file entry and in sysservers.
The with_proxydb indicates that proxy databases are created on the secondary companion for all databases other than system databases. Any subsequent databases that are added also create proxy databases.
login_name is the name of the user performing this cluster operation (they must have both the ha_role and sa_role).
password is the password of the person performing this cluster operation.
cluster_login The login that the high availability subsystem uses to log in to the companion to control it. This login must exist in the primary before running sp_companion...configure and must have sa_role and ha_role.
cluster_login_password is the user’s password for logging in to the cluster.
You must execute the above command only from the secondary companion.
This example configures an Adaptive Server named MONEY1 as a primary companion. Issue the following command from the secondary server PERSONNEL1:
1> sp_companion "MONEY1", configure, with_proxydb, sa, MyPassword, sa_cluster_login, MyClusterPassword 2> go
Server 'PERSONNEL1' is alive and cluster configured. Step: Access verified from Server:'PERSONNEL1' to Server:'MONEY1' Server 'MONEY1' is alive and cluster configured. Step: Access verified from Server:'MONEY1' to Server:'PERSONNEL1' (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 'PERSONNEL1' and 'MONEY1' 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 when run sp_companion, you see these messages:
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
Before you configure the companions for symmetric configuration, you must first configure them for asymmetric configuration.
See “Asymmetric Companion Configuration” for more information about asymmetric configuration.
