HDR and Client Redirection
Posted in 2006
Topics: High Availability & Replication, Versions, Editions & End-of-Life
Hi all, I currently set up a HDR environment with IDS 10.0 on Suse Linux/Power. Works like a charm. Next thing I need to investigate is how to redirect the cleints to the new primary after a failover. Coming from DB2 I would prefer the method where I specify the alternate server via DBPATH environment variable at the client side(looks similar to DB2's client rerouting for me). This works fine as long as the failed primary is down. But when I reintegrate the former primary as new standby I run into problems. The new standby will go online in "Read Only" mode - thus the clients will connect to him because their INFORMIXSERVER variable still contains its name. Am I missing something here or is this works as designed ? Can I prevent the secondary from being read-only ? Which method for client redirection do you use out there ? I searched the docs that I know - but found only 2 chapters in IDS Admin Guide. Any other docs available ? TIA for any answer Joachim
Joachim, you can do it this way: sqlhosts file: myServer group - - myServer1 onsoctcp myHost1 myPort1 g=myServer myServer2 onsoctcp myHost2 myPort2 g=myServer setup HDR pair using myServer1 and myServer2. for your client, set INFORMIXSERVER=myServer HTH, Karl Ostner "Joachim Klassen" <JoKlassen@email. com> To Sent by: informix-list@iiug.org informix-list-bou cc nces@iiug.org Subject HDR and Client Redirection 03/14/2006 10:19 AM Hi all, I currently set up a HDR environment with IDS 10.0 on Suse Linux/Power. Works like a charm. Next thing I need to investigate is how to redirect the cleints to the new primary after a failover. Coming from DB2 I would prefer the method where I specify the alternate server via DBPATH environment variable at the client side(looks similar to DB2's client rerouting for me). This works fine as long as the failed primary is down. But when I reintegrate the former primary as new standby I run into problems. The new standby will go online in "Read Only" mode - thus the clients will connect to him because their INFORMIXSERVER variable still contains its name. Am I missing something here or is this works as designed ? Can I prevent the secondary from being read-only ? Which method for client redirection do you use out there ? I searched the docs that I know - but found only 2 chapters in IDS Admin Guide. Any other docs available ? TIA for any answer Joachim _______________________________________________ Informix-list mailing list Informix-list@iiug.org http://www.iiug.org/mailman/listinfo/informix-list