Even for some parameters that control the behavior of the secondary server, the value on the primary server is the value that determines the behavior. The principle is that all safeness and durability parameters are controlled by the primary server. For example, the primary server reads the value of the HotStandby.2SafeAckPolicy parameter and sends that value to the secondary server to use. The value stored in the solid.ini file on the secondary server is used only if the secondary server becomes the primary server.

The following parameter values that are set on the primary server take precedence over the values set on the secondary server:

When the command hsb connect is run, the following primary server parameter values take precedence: