Re: Domino DB access in a High Availability environment.

Right now I have SystemA.
SystemA runs our ERP and has domino servers DOM01A, DOM02A, DOM03A,
DOM04A.
SystemB is a Mimix backup of our ERP and has no domino data or software.
Mail2 has Domino servers DOM01B, DOM02B, DOM03B, DOM04B.
Mail3 has Domino servers DOM01C, DOM02C, DOM03C, DOMP4C.
DOM01A, DOM01B, DOM01C are clustered.
DOM02A, DOM02B, DOM02C are clustered.
and so on.

On Mail2 we have
ADDRDBDIRE RDB(SYSTEM) RMTLOCNAME(system *IP)
On SystemA we have
ADDRDBDIRE RDB(SYSTEM) RMTLOCNAME(*LOCAL *IP)
On systemB we have the same
ADDRDBDIRE RDB(SYSTEM) RMTLOCNAME(*LOCAL *IP)
Notice, no rdb for either systema or systemb? Instead systemA and systemB
both think their local entry is just system.

If a domino application running on DOM01B on Mail2 tries to execute
If Not Con.ConnectTo ("SYSTEM", "UserID", "Password") Then Exit sub
and our DNS points SYSTEM to the same IP address as systemA then it should
connect to systemA and process.
If during the switch the dns starts pointing SYSTEM to the same IP address
as systemB then the domino app should process DB2 data on systemB.

The problem is if you run Domino on the same server as your DB2 server, as
we do with DOM01A on SystemA, then it will ignore the DNS and run the
Domino application on the local system because of the ADDRDBDIRE there for
SYSTEM.

If I change SystemA from
ADDRDBDIRE RDB(SYSTEM) RMTLOCNAME(*LOCAL *IP)
to
ADDRDBDIRE RDB(SYSTEMA) RMTLOCNAME(*LOCAL *IP)
and SystemB from
ADDRDBDIRE RDB(SYSTEM) RMTLOCNAME(*LOCAL *IP)
to
ADDRDBDIRE RDB(SYSTEMB) RMTLOCNAME(*LOCAL *IP)
and try the sample code of
If Not Con.ConnectTo ("SYSTEMA", "UserID", "Password") Then Con.ConnectTo
("SYSTEMB", "UserID", "Password")
The application will try to connect to SYSTEMA as soon as it can. but we
may not want it to because we're in failover mode and while you can
connect to systema we'd rather you process the data on systemb and let
Mimix replicate the changes over.

Rob Berendt