Re: Can I refuse all connections except replication?

On Fri, 26 Sep 2003 14:05:20 -0400, Dave Thacker wrote: Set up the replication group on all clients with the 'primary' server entry immediately following the groupname entry and the 'secondary' server entry following that and specified in the group record as the error connection (e=). Then if you use the IDS group definition as the connection name, then instead of using DNS aliasing to redirect connections when the primary is brought back online you only need to take the 'secondary' down to single user mode trashing existing connections (onmode -u) then bring it back up to online mode (onmode -m). When the users or app servers reconnect they will see the primary. Art S. Kagel > 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? > > TIA > > Dave Thacker