It should be possible to define shadows of a database
on server-level instead in the primary database.
Shadows are great to keep a DB running even if the
primary DB goes down.
But if the the primary DB goes down when nobody is
connected to it, then the "connection" between the
primary DB and its shadow DBs are lost - the admin has
to gfix the problem by hand.
If the server "knows" the primary DB and all shadows of
it, it can redirect a connecting client automatically
from the failed primary DB to one of the shadow DBs.
Submitted by: ohenri (ohenri)
SFID: 1411237# Submitted By: ohenri
It should be possible to define shadows of a database on server-level instead in the primary database.
Shadows are great to keep a DB running even if the primary DB goes down. But if the the primary DB goes down when nobody is connected to it, then the "connection" between the primary DB and its shadow DBs are lost - the admin has to gfix the problem by hand.
If the server "knows" the primary DB and all shadows of it, it can redirect a connecting client automatically from the failed primary DB to one of the shadow DBs.