Defining HotStandby configuration on primary and secondary servers
The solid.ini configuration files on each server must have the following minimum configuration information in the [HotStandby] sections of the solid.ini files:
▪ The HotStandby.HSBEnabled parameter must be set to yes.
If the HotStandby.HSBEnabled is not set to yes, the server starts as a non-HSB server and HSB replication is not used.
▪ TheHotStandby.Connect parameter must be set. This parameter defines the network name that is used to connect to the other server (either primary or secondary). If you do not set this parameter in the solid.ini file, the server can run only in the states that do not require a connection, for example, PRIMARY ALONE, SECONDARY ALONE, and STANDALONE. When the server is running, you can set or change this parameter by using the ADMIN COMMAND 'parameter' command.
▪ The HotStandby.Connect string for each server must match the Com.Listen string of the other server. For example, if the server on Server1 is listening on tcp 2315, the HotStandby.Connect parameter on the server at Server2 must be set to tcp node_name | ip_address 2315. The node_name or ip_address of the server on Server1 must be specified also.
Example: Server1 minimum configuration
[Com] Listen=tcp 2315
[HotStandby] HsbEnabled=yes
Connect=tcp server2 2325 ;The server on Server1 connects to the server on Server2 ;using the connect string 'tcp node2 2325': ;The host name 'server2' can be replaced by IP address.
Example: Server2 minimum configuration
[Com] Listen=tcp 2325
[HotStandby] HsbEnabled=yes
Connect=tcp server1 2315 ;The server on Server2 connects to the server on Server1 ;using the connect string 'tcp server1 2315'. ;The host name 'server1' can be replaced by IP address.