To use two OpenSwitch servers effectively in a warm standby environment, you must use features provided by both OpenSwitch and the connectivity software. You can then configure your environment so that users are switched from a primary OpenSwitch server to the secondary OpenSwitch server upon failover. This is also described in this section as a rollover of the connections.
You can use the redundant RCM to funnel DSS users to
the standby Adaptive Server.
Configuring a redundant environment is complex, and you must be aware of the following constraints:
You must add an entry to the sql.ini (Windows) or interfaces (UNIX) file for each OpenSwitch server; one for the primary OpenSwitch server and one for the secondary OpenSwitch server.
You must add a second query line to each OpenSwitch server entry that contains redundant connection information to be used during a rollover.
The configuration files for the primary RCM and redundant RCM instances can be identical.
See “Setting up a configuration file for two RCM instances” to view an example of an RCM configuration file for a redundant OpenSwitch environment.
If you use batch files to run the RCM, you must create two batch files or scripts, one for each RCM instance.
The redundant RCM must be started at the command line using the rcm command with the -R flag. See “Starting and stopping the RCM” for more information about the -R flag.
