In order to expand and collapse the table of contents, you must enable JavaScript in the browser.
(Collapse Contents)
Title Page
Preface
Chapter 1 Overview of Database Multiplexing Mode
1.1 What is Database Multiplexing Mode
1.1.1 Monitoring Using Database Multiplexing Mode
1.1.2 Referencing on the Standby Server
1.1.2.1 If Prioritizing the Main Job on the Primary Server
1.1.2.2 If Performing the Referencing Job on the Synchronous Standby Server
1.2 System Configuration for Database Multiplexing Mode
1.2.1 Mirroring Controller Resources
1.2.1.1 Database Server Resources
1.2.1.2 Arbitration Server Resources
1.2.2 Mirroring Controller Processes
1.2.2.1 Database Server Processes
1.2.2.2 Arbitration Server Process
1.2.3 Redundancy of the Admin and Log Transfer Networks
1.2.4 Notes on CPU Architecture and Products
1.3 Deciding on Operation when a Heartbeat Abnormality is Detected
1.4 Security in Database Multiplexing
1.4.1 Authentication of the Standby Server
1.4.2 Encryption of Transaction Logs Transferred to the Standby Server
Chapter 2 Setting Up Database Multiplexing Mode
2.1 Installation
2.2 Preparing for Setup
2.2.1 Preparing the Database Server
2.2.1.1 Preparing the Backup Disk
2.3 Setting Up the Arbitration Server
2.3.1 Configuring the Arbitration Server
2.3.2 Creating a User Command for the Arbitration Server
2.3.3 Starting the Mirroring Controller Arbitration Process
2.4 Setting Up the Primary Server
2.4.1 Setting Up Database Multiplexing Mode on the Primary Server
2.4.2 Creating, Setting, and Registering the Primary Server Instance
2.4.3 Starting Mirroring Controller on the Primary Server
2.5 Setting Up the Standby Server
2.5.1 Setting Up Database Multiplexing Mode on the Standby Server
2.5.2 Creating, Setting, and Registering the Standby Server Instance
2.5.3 Starting Mirroring Controller on the Standby Server
2.6 Creating a User Command for a Database Server
2.7 Confirming the Streaming Replication Status
2.8 Checking the Connection Status
2.8.1 Checking the Connection Status on a Database Server
2.8.2 Checking the Connection Status on the Arbitration Server
2.9 Creating Applications
2.9.1 Application Connection Server Settings
2.10 Checking the Behavior
2.11 Tuning
2.11.1 Tuning to Stabilize the Database Multiplexing Mode
2.11.2 Tuning to Stabilize Queries on the Standby Server
2.11.3 Tuning to Stabilize Queries on the Standby Server (when Performing Frequent Updates on the Primary Server)
2.11.4 Tuning for Optimization of Degradation Using Abnormality Monitoring
2.11.4.1 Tuning for Abnormality Monitoring of the Operating System or Server
2.11.4.1.1 Tuning Abnormality Monitoring for Operations that Use an Arbitration Server for Automatic Degradation
2.11.4.1.2 Tuning Abnormality Monitoring for Operations that Perform Automatic Degradation by Calling a User Command that Determines Degradation
2.11.4.1.3 Tuning Abnormality Monitoring for Operations that Notify Messages
2.11.4.1.4 Tuning Abnormality Monitoring for Operations that Perform Automatic Degenerate Unconditionally due to Heartbeat Abnormality
2.11.4.2 Tuning for Abnormality Monitoring of Darabase Processes
2.11.4.3 Tuning for Abnormality Monitoring of Streaming Replication
2.11.4.4 Tuning for Disk Abnormality Monitoring
2.12 Setting Automatic Start and Stop of Mirroring Controller and Multiplexed Instances
2.13 Setting Automatic Start and Stop of the Mirroring Controller Arbitration Process
2.14 Backup Operation
2.14.1 Backing up Database Multiplexing Mode Information
2.14.2 Database Backup Operation
Chapter 3 Operations in Database Multiplexing Mode
3.1 Starting and Stopping the Mirroring Controller Arbitration Process
3.1.1 Starting the Mirroring Controller Arbitration Process
3.1.2 Stopping the Mirroring Controller Arbitration Process
3.2 Starting and Stopping Mirroring Controller
3.3 Checking the Database Multiplexing Mode Status
3.3.1 Checking the Status of the Database Server
3.3.2 Checking the Status of the Arbitration Server
3.4 Manually Switching the Primary Server
3.5 Manually Disconnecting the Standby Server
3.6 Action Required when a Heartbeat Abnormality is Detected
3.7 Monitoring Mirroring Controller Messages
3.8 Server Maintenance
3.8.1 Rolling Updates
3.8.2 Stopping for Maintenance
3.8.3 Arbitration Server Maintenance
3.9 Changes in Operation
3.9.1 Changes Required when the Standby Server is Stopped
3.9.2 Changing from Single Server Mode to Database Multiplexing Mode
3.9.3 Changing from Database Multiplexing Mode to Single Server Mode
3.9.4 Changing to Database Multiplexing Mode when the Arbitration Server is Used for Automatic Degradation
3.9.5 Changing Parameters
3.9.6 Uninstalling in Database Multiplexing Mode
Chapter 4 Action Required when an Error Occurs in Database Multiplexing Mode
4.1 Action Required when Server Degradation Occurs
4.1.1 Operations when the Server has Started Degrading after a Switch has Occurred
4.1.1.1 Identify Cause of Error and Restore the Standby Server
4.1.1.1.1 Stop Mirroring Controller
4.1.1.1.2 Recovery of the Mirroring Controller management directory
4.1.1.1.3 Identify cause of error and perform recovery
4.1.1.2 Rebuild the Standby Server
4.1.1.3 Failback of the Primary Server
4.1.2 Operations when the Server has Started Degrading after a Disconnection has Occurred
4.1.2.1 Identify Cause of Error and Restore the Standby Server
4.1.2.1.1 Stop Mirroring Controller
4.1.2.1.2 Recovery of the Mirroring Controller management directory
4.1.2.1.3 Identify cause of error and perform recovery
4.1.2.2 Rebuild the Standby Server
4.1.3 Addressing Errors During Degrading Operation
4.2 Action Required when Automatic Switch Fails
4.3 Action Required when Automatic Disconnection Fails
4.4 Action Required when All Database Servers or Instances Stopped
4.5 Recovering from an Incorrect User Operation
Chapter 5 Managing Mirroring Controller Using WebAdmin
5.1 Mirroring Controller Setup
5.2 Edit Mirroring Controller Setup
5.3 Mirroring Controller Configuration
5.4 Stopping Mirroring Controller
5.5 Starting Mirroring Controller
5.6 Disabling Failover Mode
5.7 Enabling Failover Mode
5.8 Deleting Mirroring Controller Setup
5.9 Status Update after Failover
5.10 Action Required when an Error Occurs in the Combined Admin Network and Log Transfer Network
5.11 Performing Automatic Degradation Using the Arbitration Server
Appendix A Parameters
A.1 Parameters Set on the Primary Server
A.2 Parameters Set on the Standby Server
A.3 Network Configuration File
A.4 Server Configuration File
A.4.1 Server Configuration File for the Database Servers
A.4.2 Arbitration Configuration File
Appendix B Supplementary Information on Building the Primary Server and Standby Server on the Same Server
B.1 Backup Data Storage Destination Directory
B.2 How to Execute the mc_ctl Command
Appendix C User Commands
C.1 Fencing Command
C.2 Arbitration Command
C.3 State Transition Commands
C.3.1 Post-switch Command
C.3.2 Pre-detach Command
C.3.3 Post-attach Command
Appendix D Notes on Performing Automatic Degradation Immediately after a Heartbeat Abnormality
Appendix E WebAdmin Disallow User Inputs Containing Hazardous Characters
Appendix F Collecting Failure Investigation Data
Top
(Collapse Contents)
Title Page
