High Availability Guide
Introduction to solidDB® HotStandby
Key features of HotStandby
HotStandby API (HSB admin commands)
Basic HotStandby server scheme
Server HotStandby states
Replication modes in HotStandby
Durability and logging
Load balancing of read-only workloads
HotStandby and SMA
HotStandby and advanced replication
Performance and HotStandby
High Availability Controller (HAC)
Recognized failures
Controlling database server processes
External Reference Entity (ERE)
Networking in HAC
HAC logging
High Availability Manager (sample)
Getting started with HotStandby
HotStandby quick start procedure
HotStandby with HAC quick start procedure
Starting and stopping HA Controller
Summary of startup sequences
Administering and configuring HotStandby
Basics of HotStandby administration
Querying HotStandby configuration parameters
Modifying HotStandby configuration parameters
Configuring HotStandby
Defining primary and secondary node HotStandby configuration
Setting HotStandby server wait time to help detect broken or unavailable connections
Defining transaction durability level
Defining name and location for HotStandby database operation
Defining primary server behavior during a secondary failure
Ensuring that Primary and Secondary parameter values are coordinated
Determining whether the Primary settings take precedence over the Secondary settings
Configuring HA Controller and HA Manager
Administering HotStandby with ADMIN COMMANDs (HotStandby API)
Overview of administration tasks
Performing HotStandby recovery and maintenance
Switching server states
Shutting off HotStandby operations
Synchronizing primary and secondary servers
Connecting HotStandby servers
Checking HotStandby status
Verifying HotStandby server states
Choosing which server to make primary
Changing a HotStandby server to a non-HotStandby server
Performance tuning
Tuning replication performance with safeness and durability levels
Tuning netcopy performance
Tuning database catchup performance
Special considerations for using solidDB® with HotStandby
Transaction isolation level and in-memory tables
Network partitions and dual primaries
Running out of space for transaction logs
Throttling and multiprocessing in Secondary
Configuring for lower cost versus higher safety
Reducing cost: N + 1 spare and N + M spares scenarios
Increasing reliability: 2N + 1 spare and 2N + M spare scenarios
How solidDB® HSB supports the N+1 (N+M) and 2N+1 (2N+M) approaches
Using HAC with spares
Using HotStandby with applications
Connecting to HotStandby servers
Choosing the connectivity type
Transparent Connectivity
Defining the Transparent Connectivity connection
Failure transparency in Transparent Connectivity
Load balancing in Transparent Connectivity
Handling TC Info contradictions
Basic Connectivity
Reconnecting to primary servers from applications
Reconnecting to secondary servers
Defining timeouts between applications and servers
Application read timeout option
Specifying -C option in the connect parameters
Configuring SMA with HotStandby
Configuring advanced replication with HotStandby
Failure handling with High Availability Controller (HAC)
Primary database fails
Secondary database fails
Primary node fails
Secondary node fails
HotStandby link fails
Server is unresponsive to external clients
Upgrading (migrating) HotStandby servers
Cold migration procedure
Hot migration procedure
Hot migration procedure using netcopy
HotStandby configuration parameters
Server-side parameters
Cluster section
HotStandby section
Client-side parameters
Com section
TransparentFailover section
High Availability Controller (HAC) parameters
High Availability Manager (HAM) configuration parameters
Configuration file examples
The solid.ini configuration file
The solidhac.ini configuration file
The HAManager.ini configuration file
Error codes for HotStandby
HotStandby errors and status codes
High Availability Controller errors and status codes
solidDB® database errors for HotStandby
solidDB® table errors
solidDB® communication errors
HotStandby and HAC ADMIN COMMANDs
HotStandby commands (ADMIN COMMAND)
High Availability Controller commands (ADMIN COMMAND)
Server state transitions
HotStandby state transition diagram
HotStandby system events
Watchdog sample
HotStandby configuration using Watchdog
How the Watchdog application works
System design issues
Watchdog configuration
Using the sample Watchdog application
Failure situations and Watchdog actions
Primary is down
Secondary is down
Watchdog is down
Communication link between Primary and Secondary is down
Communication link between the Watchdog and Primary is down
Communication link between the Watchdog and Secondary is down
Communication links between the Watchdog and Primary, and between the Primary and Secondary, are down Scenario
Communication links between the Watchdog and Secondary, and between the Primary and Secondary, are down
Watchdog section of the solid.ini configuration file
High Availability Guide
Watchdog section of the solid.ini configuration file
This site works best with JavaScript enabled