This chapter describes how to set up database multiplexing mode, and how to check it.
Users who perform setup and operations on the database server
Setup and operations of the database server must be performed by the instance administrator user.
Users who perform setup and operations on the arbitration server
The following users may perform setup and operations on the arbitration server when it is used for automatic degradation.
Any operating system user.
Any user with administrator privileges. This user must be assigned the "Log on as a service" user right.
Point
Mirroring Controller selects a database superuser as the user who will connect to the database instance. This enables instance administrator users and database superusers who operate the Mirroring Controller commands to run database multiplexing mode in different environments.
The application name for connecting to the database instance is "mc_agent".
Before starting the setup, ensure that the times in the primary server, standby server and arbitration server match, by using the operating system time synchronization feature, for example.
The tolerated difference is approximately one second.
If the system times are not synchronized (because the tolerated difference is exceeded, for example), problem investigation may be affected.
Because the ping command of the operating system is used for heartbeat monitoring of the database server, configure the network so that ICMP can be used on the admin network and the arbitration network. Refer to the relevant operating system procedure for details.
The setup procedure is shown in the table below. However, the procedure on the arbitration server should be performed only when the arbitration server is used for automatic degradation. A distinction is made between the procedures on the primary server and standby server according to whether the arbitration server is used.
Step | Task | Refer to | ||
|---|---|---|---|---|
Primary server | Standby server | Arbitration server | ||
1 | Installation | |||
2 | Preparing the database server | Preparing the arbitration server | ||
3 | Configuring the arbitration server | |||
4 | Creating a user exit | |||
5 | Starting the arbitration process | |||
6 | Setting up database multiplexing mode | 2.4.1 Setting Up Database Multiplexing Mode on the Primary Server | ||
7 | Creating, setting, and registering the instance | 2.4.2 Creating, Setting, and Registering the Primary Server Instance | ||
8 | Creating a user exit | |||
9 | Starting Mirroring Controller | |||
10 | Setting up database multiplexing mode | 2.5.1 Setting Up Database Multiplexing Mode on the Standby Server | ||
11 | Creating, setting, and registering the instance | 2.5.2 Creating, Setting, and Registering the Standby Server Instance | ||
12 | Creating a user exit | |||
13 | Starting Mirroring Controller | |||
14 | Confirming the streaming replication status | |||
15 | Checking the connection status | |||
16 | Checking the connection status | |||
17 | Checking the connection status | 2.8.2 Checking the Connection Status on the Arbitration Server | ||
18 | Creating applications | |||
19 | Checking the behavior | |||
Explanations for each step are provided below.
Information
The setup procedure is also the same when changing the mode on a single server to database multiplexing mode. In this case, omit the installation of Fujitsu Enterprise Postgres and the creation of the instance.
Refer to "3.9.2 Changing from Single Server Mode to Database Multiplexing Mode" for details.
The primary and standby server can be pseudo-configured on the same server for system testing, for example. In this case, the setup can be performed using the same procedure, however there will be some supplementary steps.
Before performing the setup, refer to "Appendix B Supplementary Information on Building the Primary Server and Standby Server on the Same Server".
