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 "6.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 B 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 excluding spaces 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.
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. Accordingly, users other than the instance administrator user are prevented from operating Mirroring Controller.
Register in /etc/services the port number of the standby server that was specified in the network.conf file, because programs such as WebAdmin use it to search for available port numbers.
Register any name as the service name.
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.
Set "Read" permission for the instance administrator user only. If users other than the instance administrator user are granted access privileges, the mc_ctl command will not work.
