6.3.1 Setting up Database Multiplexing Mode on the Primary Server

This section explains how to set up database multiplexing mode on the primary server.

In database multiplexing, the files that are required for operations are managed in the Mirroring Controller management directory.

There is one Mirroring Controller management directory for each instance.

Note

Do not place the Mirroring Controller management directory in a directory managed by Symfoware Server, otherwise it may be deleted by mistake with the directories managed by Symfoware Server, and an old version of files may be restored.
Start Mirroring Controller first, from the primary server. If it is started from the standby server, a switch will occur.

See

Refer to "Preparing Directories for Resource Deployment" in the Installation and Setup Guide for Server for details on the directories that are managed by Symfoware Server.
Refer to "mc_ctl" in Reference for information on the command.
Refer to "Appendix B Parameters" for details on each parameter to be edited for the setup.

Perform the following procedure:

Log in to the primary server.
Create the Mirroring Controller management directory that will store the files required by database multiplexing.
Use ASCII characters excluding spaces in the Mirroring Controller management directory.
Additionally, grant "Write" permission to the instance administrator user for the Mirroring Controller management directory.
In the network.conf file, define the network configuration that will link between the Mirroring Controller processes.
Create the network.conf file in the Mirroring Controller management directory, based on the sample file. In the network.conf file, set "Read" permission for the instance administrator user only.
If users other than the instance administrator user are granted access, the mc_ctl command will not work. In this way, users other than the instance administrator user are prevented from operating Mirroring Controller.
```
Path of the sample file
```
```
/installDir/share/mc_network.conf.sample
```
In the network.conf file, specify the host name (or IP address) and port number of the primary server and standby server, and define the network configuration that will link between the Mirroring Controller processes.
Refer to "B.3 Network Configuration File" for details.
A definition example is shown below.
In this example, the Mirroring Controller default port number 26540 is specified, and "server1" and "server2" represent any server identifiers.
```
Example)
```
```
server1 192.0.2.100 26540
server2 192.0.2.110 26540
```
Ensure that the port numbers for the primary and standby server do not conflict with other software.
Register in /etc/services the port number of the primary server, because programs such as WebAdmin use it to search for available port numbers.
Register any name as the service name.

Define the information related to Mirroring Controller monitoring and control in the serverIdentifier.conf file.

Create the serverIdentifier.conf file in the Mirroring Controller management directory, based on the sample file.

In the serverIdentifier.conf file, set "Read" permission for the instance administrator user only. If users other than the instance administrator user are granted access, the mc_ctl command will not work.

As the file name for the serverIdentifier.conf file, use the server identifier name that was specified in the network.conf file in step 3.

Path of the sample file

/InstallDir/share/mc_server.conf.sample

Set the parameters shown in the table below in the serverIdentifier.conf file.

Table 6.1 Parameters
Parameter	Content specified	Remarks
db_instance	'dataStorageDestinationDir'	Enclose the directory within single quotation marks ('). Use ASCII characters excluding spaces to specify this parameter.
db_instance_password	'Password of the instance administrator user'	If password authentication is performed, you must specify this parameter in the settings used when Mirroring Controller connects to a database instance. Use ASCII characters excluding spaces to specify this parameter. Enclose the name within single quotation marks (').
syslog_ident	'programName'	Specify the program name to be used to identify the Mirroring Controller messages in the system log. Use ASCII characters excluding spaces to specify this parameter. Use the same program name as the parameter in the postgresql.conf file ensures that the Mirroring Controller output content can be referenced transparently, so log reference is easy. Enclose the name within single quotation marks (').
heartbeat_interval	800 (milliseconds)	The time until an operation, such as the switch of the primary server, is performed after it was detected that there was no response, is calculated according to the following formula: heartbeat_timeout (seconds) x heartbeat_retry (count) = 1 x 2 = 2 (seconds) According to this setting, errors are monitored at 800-millisecond intervals, and if there were two successive occurrences when there was no response for a duration of one second, the operation to switch the primary server, or disconnect the standby server from the primary server, is performed.
heartbeat_timeout	1 (second)
heartbeat_retry	2 (count)