Abstract
Informix Dynamic Server (IDS) provides a simple way to replicate a whole instance to a hot standby system, namely
High-availability Data Replication (HDR). The similar
Remote Standalone Secondary (RSS) mode has some additional features, but is normally only used in addition to HDR when there are more than two nodes in a cluster, as fail-over requires more steps. Note that a passive replica not running any workload does not require a licence.
In either case, a group can be defined for use in client connection details instead of a specific Informix server name, so that the session is routed to whichever is currently the primary in a pair. This is done in the
sqlhosts file, except for non-Java APIs on Windows where the
Setnet32 app maintains equivalent registry entries.
However, such a group only works for native protocols and not
Distributed Relational Database Architecture (DRDA). That protocol is shared with DB2, and has drivers which are better supported for some development environments such as .Net via the
IBM Data Server Driver Package on Windows.
Automating fail-over for DRDA clients therefore needs the Informix
Connection Manager (CM). This article provides an example configuration in which each server in an HDR pair runs CM as well as IDS, avoiding the need for separate CM hosts, but still providing automated fail-over without any VIP or DNS change.
[Read More…]