Warm standby applications are used to maintain a set of databases, one or more of which functions as standby copies of an active database. As clients update the active database, Replication Server copies transactions to the standby databases, maintaining consistency between them. Should the active database fail for any reason, you can switch to a standby database, making it the active database, and resume operations with little interruption.
Replication Server provides two methods for setting up a warm standby application. In both methods, the active and standby databases must be Adaptive Server databases. They can act as either a primary or replicate database with respect to other databases in the system.
One method uses the multisite availability (MSA) feature to set up an active and one or more standby databases. See Chapter 12, “Managing Replicated Objects Using Multisite Availability,” for detailed information.
The second method lets you set up an active and a single standby database, both of which must be managed by the same Replication Server. This warm standby application is considered a single logical unit in a Replication Server system. See Chapter 3, “Managing Warm Standby Applications” in the Replication Server Administration Guide Volume 2 for detailed information.
