This section explains how to set up database multiplexing mode on the standby 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.
When creating a standby server for a large database, stop job system operations, or specify a large value for the wal_keep_segments parameter.
This is because WALs generated after the standby server is built using the mc_ctl command in setup mode, but before it is started, need to be retained. However, the number of WAL segments that can be retained is constrained by the wal_keep_segments parameter.
Additionally, setting the wal_keep_segments parameter requires consideration regarding stabilization of the database multiplexing mode (refer to "8.9.1 Tuning to Stabilize the Database Multiplexing Mode" for details).
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 A Parameters" for details on each parameter to be edited for the setup.
Perform the following procedure:
Log in to the standby server.
Create the Mirroring Controller management directory that will store the files required by database multiplexing.
Use ASCII characters in the Mirroring Controller management directory.
Additionally, grant "Write" permission to the instance administrator user for the Mirroring Controller management directory.
Copy, and then deploy, the network.conf file of the primary server.
Copy the network.conf file that was defined in the primary server setup, and deploy it to the Mirroring Controller management directory of the standby server.
Register the port number of the standby server that was specified in the network.conf file in the services file, because there are programs, such as WebAdmin, that search an available port number using the services file.
Register any name as the service name.
Change the access permissions for the network.conf file.
Set "Read" permission for the instance administrator user only. If users other than the instance administrator user are granted access permissions, the mc_ctl command will not work. Accordingly, users other than the instance administrator user are prevented from operating Mirroring Controller.
Example) The following is an execution example, in which the instance administrator user is granted full access permissions as the owner when the operating system user name of the instance administrator user is "symfo". The following procedure applies when the user is logged in to the Windows server as "symfo".
> takeown /f network.conf > icacls network.conf /inheritance:r > icacls network.conf /grant symfo:F
Copy, and then deploy, the serverIdentifier.conf file of the primary server.
Copy the serverIdentifier.conf file that was defined in the primary server setup, and deploy it to the Mirroring Controller management directory of the standby server.
Note
If the primary server and standby server are to be built within the same server, change the following parameters in the serverIdentifier.conf file, ensuring that the names are not duplicated with those on the primary server:
db_instance_service_name (registered service name of the Symfoware Server instance)
mc_service_name (registered service name of Mirroring Controller)
event_source (event source name)
Change the access permissions for the serverIdentifier.conf file.
Set "Read" permission for the instance administrator user only. If users other than the instance administrator user are granted access permissions, the mc_ctl command will not work.
Example) The following is an execution example, in which the instance administrator user is granted full access permissions as the owner when the operating system user name of the instance administrator user is "symfo". The following procedure applies when the user is logged in to the Windows server as "symfo":
> takeown /f serverIdentifier.conf > icacls serverIdentifier.conf /inheritance:r > icacls serverIdentifier.conf /grant symfo:F
Configure the Windows firewall.
If the Windows firewall feature is to be enabled, you should enable the port number of Mirroring Controller that you specified in the network definition file in step 3. Refer to "C.2 Windows Firewall Settings" for details.
Register Mirroring Controller to the Windows service.
Execute the mc_ctl command in the register mode.
For the -P option of the mc_ctl command, specify the password of the operating system user who executes the command.
Example)
> mc_ctl register -M D:\mcdir\inst1 -w -f -P ********
Note
When specifying the password in the -P option of the mc_ctl command, for security reasons, you should be careful not to allow other users to access it.
Information
You can use the mc_ctl command with the -S option to specify automatic start and stop of Mirroring Controller. Refer to "8.10 Setting Automatic Start and Stop of Mirroring Controller and Multiplexed Instances" for details.
Using the service name specified in the mc_service_name parameter of the server definition file in step 5, Mirroring Controller is registered to the Windows service as shown below.
You can execute the sc qc command to check the registration status.
