With the quick start procedure, you can reach a state where your solidDB HotStandby (HSB) system is ready to serve applications.
You can use the quick start procedure to set up a pair of HSB servers on one or two computers. For evaluation purposes, you can use a single-server setup. For testing and production environments, use two computers.
To set up and run an HSB server pair, you need two networked computers. To set up your HSB servers (without any other solidDB components), complete the following steps.
Note The quick start procedure does not assume use of any other components than HSB servers. For example, the HAC is not needed. For a similar step-by-step procedure for an environment that includes HAC, see HotStandby with HAC quick start procedure.
1 Install the solidDB server on one or two computers.
▪ If you are using a single computer, create two working directories and copy the license file to each directory. An evaluation license file is available in the root directory of the solidDB installation directory.
For example, if you have installed solidDB server into the C:\solid directory, create two directories named node1 and node2:
mkdir C:\solid\node1 mkdir C:\solid\node2
▪ If you are using two computers, create a working directory on each computer and copy the license file to the directories.
For example, if you have installed solidDB server into the C:\solid directories on both computers, create a directory named server1 on one computer and a directory named server2 on the other:
Server 1 mkdir C:\solid\server1
Server 2 mkdir C:\solid\server2
2 Configure the primary and secondary servers. Create solid.ini configuration files in the working directories.
At a minimum, you must configure the HotStandby.HSBEnabled and HotStandby.Connect parameters in the solid.ini configuration file on both the primary (Server 1) and secondary (Server 2) servers:
▪ HotStandby.HSBEnabled=Yes
▪ HotStandby.Connect=connect string for the opposite HSB server
Additionally, the Com.Listen parameter must be set.
The following table describes how to set up each server depending on whether you are deploying both servers to a single computer or to separate computers.
Server
Single computer setup
Two-computer setup
Server1
C:\solid\node1\solid.ini with the following entries:
[Com] Listen=tcp 2315
[HotStandby] HsbEnabled=yes Connect=tcp 2325
The server instance Server1 connects to the Server2 instance using the connect string tcp 2325. Because the servers are on the same computer, you do not need to define a server name or IP address for Server2.
C:\solid\node1\solid.ini with the following entries:
The server on Server1 connects to the server on Server2 using the connect string tcp node2 2325. Instead of using a server name such as server2, you can use the IP address of the Server2 computer, for example, tcp 10.0.0.2 2325.
Server2
C:\solid\server2\solid.ini with the following entries:
[Com] Listen=tcp 2325
[HotStandby] HsbEnabled=yes Connect=tcp 2315
The server instance Server2 connects to the Server1 instance using the connect string tcp 2315. Because the servers are on the same computer, you do not need to define a server name or IP address for Server1.
C:\solid\server2\solid.ini with the following entries:
The server on Server2 connects to the server on Server1 using the connect string tcp node1 2315. Instead of using a server name such as server1, you can use the IP address of the Server1 computer, for example, tcp 10.0.0.1 2315.
3 Start both HSB servers the way you would start any solidDB server.
The servers read the HSB configuration information from their own solid.ini files. The state of both servers after startup is SECONDARY ALONE.
4 Choose the server that will become the primary server, and switch the state of the chosen server to PRIMARY ALONE by running the following command:
ADMIN COMMAND 'hsb set primary alone';
Note In the HSB administration commands, you can use the abbreviation hsb in place of hotstandby.
5 Connect the primary server to the secondary server by running the following command in either server:
ADMIN COMMAND 'hsb connect'
To verify that the connection was successful, run the following command:
ADMIN COMMAND 'hsb state'
In normal operation, the primary server responds with a state of PRIMARY ACTIVE. However, if the state of the primary server is something other than expected (for example, PRIMARY ALONE), the status of the connect process can be checked by running the following command:
ADMIN COMMAND 'hsb status connect'
If the result is ACTIVE, then the connect process is still active. If the result is BROKEN, the databases of the servers must be synchronized before you connect them.
6 Synchronizing the databases by running the following command in the primary server:
ADMIN COMMAND 'hsb netcopy'
Check the status of database copy process by running the command:
ADMIN COMMAND 'hsb status copy'
7 When the status check of the database copy is SUCCESS, the databases are synchronized, and the servers can be connected. Rerun the following command in either server:
ADMIN COMMAND 'hsb connect'
Verify the success by issuing the command:
ADMIN COMMAND 'hsb state'
You can now start using applications that interact with the HSB servers.