Chapter 3: Managing Warm Standby Applications

This chapter primarily describes how to set up, configure, and monitor a warm standby application between two Adaptive Server databases—the primary or active database and a single standby database. Changes to the primary database are copied directly to the warm standby database. To change or qualify the data sent, you must add table and function replication definitions.

Replication Server supports setting up and managing warm standby applications for Adaptive Server and Oracle databases. See Chapter 14, “Managing Heterogeneous Warm Standby Applications” in the Replication Server Heterogeneous Guide for detailed information on how to set up and configure a warm standby application between two Oracle databases. This chapter also describes concepts and tasks that are common to Adaptive Server and Oracle databases for managing warm standby.

You can also use multisite availability (MSA) to set up a warm standby application between Adaptive Server databases. MSA enables replication to multiple standby and replicate databases. You can choose whether to replicate the entire database or replicate (or not replicate) specified tables, transactions, functions, system stored procedures, and data definition language (DDL). See Chapter 12, “Managing Replicated Objects Using Multisite Availability,” in the Replication Server Administration Guide Volume 1 for information about setting up a warm standby application using MSA.