In 1-Safe replication, the maximum delay before a committed transaction is sent to the Secondary (in milliseconds).

5000

RW

This specifies the timing of the Secondary’s acknowledgement when it receives a transaction from the Primary.

Valid values are:

acknowledges when it has made the data durable, that is, when it has committed the data and written the data to the disk.

2-safe durable is the safest approach, and 2-safe received has the fastest response time. However, in practice, the 2-safe received mode provides in most cases sufficient guarantees for data safety hence providing the best compromise between safety and speed.

This parameter applies only if the server is using 2-safe replication.

1

RW

If this parameter is set to yes, the server is automatically put in PRIMARY ALONE state (rather than PRIMARY UNCERTAIN state) when the connection to the Secondary is broken.

no

RW

While the server is performing catchup, it also continues to service database requests from clients. You may use the CatchupSpeedRate parameter to give greater importance to responding to application requests and lower priority to catchup, or vice versa.

The speed rate is expressed as a percentage of the maximum available speed dictated by the link and Secondary throughput. Larger numbers mean more emphasis on catchup and less on servicing client requests. Valid values are 1-99.

50

RW

The Connect parameter indicates the address of the other HotStandby server in the pair.

The value of this parameter is a standard solidDB^® connect string (Basic Connectivity) or a TC-specific connect string (Transparent Connectivity).

The connect string defined with this parameter must match the server listening name of the other HotStandby server (defined with Com.Listen parameter).

If you omit this parameter in a server that you intend for HotStandby, you can set this parameter dynamically by using an ADMIN COMMAND. Until the server has a connect string, the server can only be in the states that do not involve a HotStandby connection, that is, PRIMARY ALONE, SECONDARY ALONE, and STANDALONE.

If HSBEnabled is set to no, this parameter is ignored.

For Transparent Connectivity (TC) connections with multi-home servers, the Connect parameter can be overridden with the HotStandby.TCConnect parameter.

No factory value.

RW

By specifying a connect timeout value, you can set the maximum time in seconds that a HotStandby connect operation waits for a connection to a remote machine.

The ConnectTimeout parameter is used with the following administration commands:

For example, to set the timeout to 30 seconds (30000 milliseconds):

See also PingTimeout.

0 (no timeout) Unit: 1 ms

RW

The CopyDirectory parameter in the [HotStandby] section defines a name and location for the HotStandby copy operation that is performed when the user executes the command:

For example, the parameter may look like:

If you provide a relative path for the CopyDirectory parameter, the path will be relative to the directory that holds the Primary server’s solid.ini file.

This parameter has no factory value, so if the directory is not specified in the solid.ini file, it must be provided in the copy command.

The ADMIN COMMAND 'hotstandby netcopy' is the recommended way to copy the database because it is a more flexible solution.

No factory value

RW

If this parameter is set to yes, the server may act as a HotStandby Primary or Secondary server. If this parameter is set to no, then the server may not act as a HotStandby server.

Setting this parameter to yes will implicitly define the default initial state of the server to be SECONDARY ALONE when the server first starts. Valid values are yes and no.

To use HotStandby, you must also specify the Connect parameter, either by setting it in the solid.ini file or by using an ADMIN COMMAND to set it.

no

RO

Defines the maximum size of the disk-based HSB log. The factory value: unlimited

0

Unit: 1 byte k=KB m=MB

 

When the file-based logging is disabled (Logging.LogEnabled=no), the size of the in-memory log holding transactions before they are sent to the Secondary. The value affects the time the server may stay in the PRIMARY ALONE state, before the in-memory log becomes full.

8M

Unit: 1 byte k=KB m=MB

RO

Defines the buffer size at Secondary server for storing data during netcopy. When the buffer is full, writes of netcopy data are throttled.

32M

Unit: 1 byte k=KB m=MB

RW

Controls whether data compression is used for a netcopy connection.

no

RW

Data transmission acknowledgment timeout for netcopy operation (in milliseconds)

30000 Unit: 1 ms

RW

The Primary and Secondary send “ping” messages to each other at regular intervals to make sure that they are still connected. (These pings are independent of the transaction information that the Primary sends to the Secondary.)

The value is equal to the interval (in milliseconds) between two consecutive pings sent by a server.

1000 (one second) Unit: 1 ms

RW

The parameter specifies how long a server should wait before concluding that the other server is down or inaccessible.

After the time specified (in milliseconds) has passed the server concludes that a connection is broken and changes the state accordingly.

See also ConnectTimeout.

4000 (four seconds) Unit: 1 ms

RW

This parameter is deprecated. Use the AutoPrimaryAlone parameter.

no

RW

This parameter sets the safeness level of the replication protocol.

Possible values are: 1safe, 2safe and auto

By using the auto value, you can allow the safeness level to dynamically change in relation to the durability level. If you set SafenessLevel to auto and set the durability to relaxed by using the SET DURABILITY command or the DurabilityLevel parameter, the safeness level is set to 1-safe, and when you set the durability level to strict, the safeness level is set to 2-safe. However, if DurabilityLevel is set to 2 (Adaptive Durability), the auto setting has no effect; the safeness level will always be 2-safe.

2-safe

RW

This parameter defines the number of threads that the Secondary server uses for processing write operations.

The optimal number of threads depends on the environment. In principle,

Valid values are 1–256.

4

RW/
Startup

This parameter defines the address of the other HotStandby server in the pair for a Transparent Connectivity (TC) connection, if the applications and servers need to use different networks to connect to each other (for example, when using multi-home servers).

From the application connection perspective, the address specified with this parameter precedes the address defined with the HotStandby.Connect parameter. The TC connection will thus use the server addresses specified with this parameter, while the HotStandby connection between the servers uses the server addresses defined with the HotStandby.Connect parameter.

No factory value.

RW