IP, sqlhosts, and setting up new server for Disaster Recovery

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. sending to informix-list

Rather than alter the hosts file just create a common virtual ip and ensure that is marked down on the secondary server and up on the primary 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. > > 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 #