Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Dave Thacker — — source: Usenet: comp.databases.informix
Obnoxio The Clown <obnoxio@hotmail.com> wrote in message news:<bl20dt$78q9j$1@ID-64669.news.uni-berlin.de>...
> Dave Thacker wrote:
>
> > Informix 9.30 running on AIX 4.3.3
> > I have two instances running EDR in update anywhere mode. All
> > connections are usually made to the "primary" instance. The
> > transactions flow from the "primary" to the "backup" unless we declare
> > a disaster. We use internal DNS to control where the various clients
> > on our WAN "see" the primary server. When we run a DR drill, we
> > change the DNS entry for the "primary" to the "backup". When the
> > drill is over we flip the DNS entry back. Many servers cache the
> > "disaster mode" DNS and we've found they continue to connect to
> > "backup" after DNS is changed.
> >
> > I've been asked by management if there is a way to block all TCP/IP
> > connections to the database *except* for replication connections. When
> > we resume normal operations, we'd like the "backup" database to refuse
> > all connections except those sending replication transactions from
> > the primary server.
> >
> > I don't see a mode like this anwhere in the Administrators Guide, Is
> > there a way to do this?
>
> Ay Caramba! Why don't you just use HDR?
Because HDR was a perfect bitch to set up in 7.3!
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.