1SafeMaxDelay

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

5000

RW

2SafeAckPolicy

Timing of the acknowledgement from the secondary server when the server receives a transaction from the primary server.

The following values are valid:

2-safe durable is the safest approach, and 2-safe received has the fastest response time. However, in practice, the 2-safe received mode usually provides a sufficient guarantee of data safety and provides the best compromise between safety and speed.

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

1

RW

AutoPrimaryAlone

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

no

RW

CatchupSpeedRate

Percentage of processing availability that is used to perform catchup as opposed to servicing database requests from clients.

While the server is performing catchup, it also continues to service database requests from clients. In a busy system, in order to ensure that catchup completes (reaches the live data), you can give greater priority to catchup operations than to client requests.

The catchup rate is expressed as a percentage of the maximum availability as dictated by the network link and secondary server throughput. Values larger than 50 mean more emphasis on catchup and less on servicing client requests.

For example: CatchupSpeedRate=80

Valid values are 1 to 99.

50

RW

Connect

Address of the other HotStandby server in the pair.

For example: Connect=tcp 2325

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 the Com.Listen parameter).

If you omit this parameter in a server that you intend to use 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 HotStandby.HSBEnabled is set to no, this parameter is ignored.

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

None

RW

ConnectTimeout

Maximum time (in milliseconds) that a HotStandby connect operation waits for a connection to a remote machine.

The ConnectTimeout parameter is used with the following ADMIN COMMANDs:

See also, PingTimeout.

30000

RW

CopyDirectory

Target directory for the HotStandby copy operation that is performed when the user executes the command:

For example: HotStandby.CopyDirectory=C:\solidDB\secondary\dbfiles

The path can be an absolute path or relative to the solidDB working directory and must use the conventions of your operating system. For example, in Windows environments, if the path contains white space characters, the path must be enclosed in double quotation marks. If the server runs on a UNIX operating system, path separators must be slashes instead of backslashes.

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.

None

RW

HSBEnabled

If set to yes, the server can act as a HotStandby primary or secondary server.

If set to no, then the server cannot act as a HotStandby server.

Setting this parameter to yes implicitly defines the default initial state of the server to be SECONDARY ALONE when the server first starts.

To use HotStandby, you must also specify the Connect parameter.

no

RO

MaxLogSize

Maximum size (in bytes) of the disk-based HotStandby log.

A value of 0 means there is no maximum size.

Follow the value with G (to specify a value in GB), K (to specify a value in KB), or M (to specify a value in MB).

For example: MaxLogSize=500M

0

RO

MaxMemLogSize

When the file-based logging is disabled (Logging.LogEnabled=no), the size (in bytes) of the in-memory log holding transactions before they are sent to the secondary server.

Follow the value with G (to specify a value in GB), K (to specify a value in KB) or M (to specify a value in MB).

For example: MaxMemLogSize=150M

The value affects the time the server can stay in the PRIMARY ALONE state, before the in-memory log becomes full.

100M

RO

NetcopyCopyLog

If set to yes, the hsb netcopy command copies the solidDB log files as well as the database files.

Copying logs is useful for CREP replication with HotStandby. If the log files are copied, the log positions of the primary server are also valid on the secondary server after the copy is complete.

no

RO

NetcopyReceiveBufferSize

Buffer size (in bytes) in the secondary server for storing data during netcopy. When the buffer is full, writes of netcopy data are throttled.

Follow the value with G (to specify a value in GB), K (to specify a value in KB) or M (to specify a value in MB).

For example: NetcopyReceiveBufferSize=64M

32M

RW

NetcopyRpcCompress

If set to yes, data compression is used for a netcopy connection.

no

RW

NetcopyRpcTimeout

Data transmission acknowledgment timeout (in milliseconds) for netcopy operation.

30000

RW

PingInterval

Interval (in milliseconds) between two consecutive pings sent by a server.

The primary and secondary servers 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 server sends to the secondary server.)

1000 (one second)

RW

PingTimeout

Time (in milliseconds) that a server should wait before concluding that the other server is down or inaccessible.

After the time specified has passed, the server concludes that a connection is broken and changes the state accordingly.

See also, ConnectTimeout.

4000 (four seconds)

RW

PrimaryAlone

This parameter is deprecated. Use the AutoPrimaryAlone parameter instead.

no

RW

SafenessLevel

Safeness level of the replication protocol.

Possible values are 1safe, 2safe, and auto.

If set to auto, the safeness level depends on the durability level (as set by using the SET DURABILITY statement or the Logging.DurabilityLevel parameter, see Logging section):

2safe

RW

SecondaryThreads

Number of threads that the secondary server uses for processing write operations.

The optimal number of threads depends on the environment and requires experimenting with loads that are typical for your environment. In principle, the more processing capacity (cores) the computer has, the higher you can set the value of this parameter. However, excessive use of threads is not likely to improve performance.

Valid values can be 1 to 256.

4

RW/
Startup

TCConnect

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 takes priority over the address specified with the HotStandby.Connect parameter. The TC connection uses server addresses specified with this parameter, while the HotStandby connection between the servers uses the server addresses defined with the HotStandby.Connect parameter.

None

RW