Example 2: Remote Active Secondary
The above image of active hot-standby configuration illustrates the deployment of a single secondary database server operating in an active ‘hot standby’ mode. The secondary server is installed at a different location to the primary. In this example, the secondary database provides a remote ‘hot standby’ database while at the same time supporting read-only database access.
The main differences between this and the prior scenario are:
-
The secondary database is hosted in a remote location to the primary host system
-
There are active nodes connected to the secondary database server supporting inquiry transactions
Disaster recovery strategies require a means to quickly relocate processing from the primary processing center to a site in a different geographic location. In this scenario, the secondary database is located at Site 2 in a different geographic location to the primary database at Site 1, and can be used to restore database availability following a catastrophic failure that renders the primary processing site or hardware unavailable for any reason.
