RE: IP, sqlhosts, and setting up new server for Disaster Recovery
Posted in 2004
Topics: Connectivity: ODBC / JDBC / .NET, Server Administration, Networking & sqlhosts Configuration, Platform-Specific Issues, Versions, Editions & End-of-Life
Doug Fossmeyer wrote > > We are creating a 2nd almost identical HP-UX database server > for disaster > recovery. For purposes of a smooth transition, can folks > review our plan > and find the holes or issues? Assume that the onconfig, > dbserver name, > alias, nettypes, etc are identical on both machines. > 1. hp_prod goes down > 2. hp_disaster_recovery is brought up and has ip address > changed to what > hp_prod was. > 3. /etc/hosts file is modified to reflect new ip address > 4. execute net stop and net start > 5. bring IDS 7.3 up > 6. start the openlink connection pooling software > 7. Clients should be able to connect using ip odbc connection software > > Any helpful suggestions are welcome. If you are under Unix you should be able to use ip aliasing. This is when a server uses an IP address for the Informix instance in addition to its ordinary address. As part of the bringing up of the recovery machine it can check this address is not up before proceeding. This works beautifully for us without modification to /etc/hosts or sqlhosts. No idea if this is available for Windows. Colin Bull c.bull@videonetworks.com sending to informix-list
IP aliasing is available on Windows, at the least the server products but in this case it's not required as the clients are all odbc so the which server has the ip is irrelevant. Colin Bull wrote: > > Doug Fossmeyer wrote > > > > > We are creating a 2nd almost identical HP-UX database server > > for disaster > > recovery. For purposes of a smooth transition, can folks > > review our plan > > and find the holes or issues? Assume that the onconfig, > > dbserver name, > > alias, nettypes, etc are identical on both machines. > > 1. hp_prod goes down > > 2. hp_disaster_recovery is brought up and has ip address > > changed to what > > hp_prod was. > > 3. /etc/hosts file is modified to reflect new ip address > > 4. execute net stop and net start > > 5. bring IDS 7.3 up > > 6. start the openlink connection pooling software > > 7. Clients should be able to connect using ip odbc connection software > > > > Any helpful suggestions are welcome. > > If you are under Unix you should be able to use ip aliasing. This is when a server uses an IP address for the Informix instance in > addition to its ordinary address. As part of the bringing up of the recovery machine it can check this address is not up before > proceeding. > > This works beautifully for us without modification to /etc/hosts or sqlhosts. > > No idea if this is available for Windows. > > Colin Bull > c.bull@videonetworks.com > > sending to informix-list -- Paul Watson # Oninit Ltd # Growing old is mandatory Tel: +44 1436 672201 # Growing up is optional Fax: +44 1436 678693 # Mob: +44 7818 003457 # www.oninit.com #