After you configure the companions for asymmetric fail over, you can set them up 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.
Issue sp_companion from the primary companion to configure it for symmetric configuration. Use syntax similar to the one for asymmetric configuration, but replace with_proxydb by NULL. See “Creating an asymmetric companion configuration”.”
In the following example, PERSONNEL1 is the secondary server of MONEY1. This is an asymmetric configuration, and will be changed to a symmetric one:
sp_companion 'MONEY1', configure, NULL, sa, Think2Odd
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
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
