Entering content frame

 Hot Standby 

Hot standby is a high availability strategy. If the active database instance fails, the hot standby enables you to switch immediately to a standby database instance that is running in parallel to the database instance that has failed.

A hot standby system consists of an active master instance (master component) and one or more standby components that are installed in a cluster configuration (see also Architecture of a Hot Standby System). On the outside, the hot standby system behaves like any normal database instance.

If an error occurs in the master instance, a standby component can take on the role of the master component automatically. This is faster than a standard cluster solution and means that no data is lost. The process is guaranteed by a special fail over mechanism in the cluster software.

Setting Up a Hot Standby System

To set up a hot standby system, you need to install a database instance that will take on the role of the master component. You then add as many standby components as you want to use.

When you initialize a new standby component, the memory management system takes the entire contents of the master component data area in a consistent state, for example, the state it was in at the point of the most recent savepoint, and copies it into the data area of the standby component.

See also:

System Requirements

Database Manager CLI: Setting Up a Hot Standby System

Database Manager GUI: Setting Up Master Components (Hot Standby) and Adding Standby Components (Hot Standby)

 

Leaving content frame