In case anyone else wants to know how to do this:


When the primary server server1 goes down:

1. Change server2 (the RSS secondary) to a standalone server – onmode -d standard.

Once server1 (the old primary) is fixed do the following:

1. (Optional) Stop the connection managers on both server1 and server2.

2. Ensure server1 is down with onmode -ky.

3. Run the hdrmkpri.sh server1_instance on server2. Check the logs to make sure this has successfully happened.

4. Run the hdrmksec.sh server2_instance on server1. Check the logs to make sure this has successfully happened.

5. Bring server2 backup using oninit -vy.

6. If you are going to leave the servers in this state restart the connection managers on server1 and server2.

Server1 should initially say Fast Recovery (Sec) and then change to Read-Only (Sec) once server2 is backup.

Server2 should say On-Line (Prim)


We now have the two servers back up and running except that the primary is now the secondary and visa versa. To get back to our original position:

1. Ensure server2 is down with onmode -ky.

2. Change server1 to a standalone server with onmode -d standard.

3. Run the hdrmkpri.sh server2_instance on server1. Check the logs to make sure this has successfully happened.

4. Run the hdrmksec.sh server1_instance on server2. Check the logs to make sure this has successfully happened.

5. Bring server1 backup using oninit -vy.

6. (Optional) Do onmode -l and onmode -c to ensure everything is up to date.

7. Check the rss server is still registered on server1 with onstat -g rss. If it is not then re-add it with onmode -d add RSS server2.

8. Change server2 back to an RSS server with onmode -d RSS server1

9. Restart the connection managers on server1 and server2.

Thanks to Art Kagel and Jarrod Teale for their help.

--
Regards
Scott Newton
R&D Solutions Specialist

< Integral >< Axon >

DDI: +64 09 302 2788
Fax: +64 09 523 8810

Axon House, 414-422 Khyber Pass Road, Newmarket 1023, Auckland
PO Box 9824, Newmarket 1023, Auckland

This correspondence is confidential, is intended for the named recipient(s)only, and may contain information that is confidential or subject to legalprofessional privilege. If you are not the intended recipient you must notuse, disclose, distribute, copy or retain it. If you have received it in error please immediately notify me by return email and delete the emails. Thank you.
________________________________
From: Art Kagel [art.kagel (AT) gmail (DOT) com]
Sent: Wednesday, 4 August 2010 22:07
To: Scott Newton
Cc: informix-list (AT) iiug (DOT) org
Subject: Re: Failover question

The standard method is to bring up the old primary, make it an RSS secondary to the new primary, then, once it has caught up, reverse them making the old primary primary again and the original RSS secondary secondary again. The second part will have to be done during a maintenance window as making the reversal will force out any connected sessions.

Art

Art S. Kagel
Advanced DataTools (www.advancedatatools.com<http://www.advancedatatools.com>)
IIUG Board of Directors (art (AT) iiug (DOT) org<mailto:art (AT) iiug (DOT) org>)

Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on my employer, Advanced DataTools, the IIUG, nor any other organization with which I am associated either explicitly, implicitly, orby inference. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves.



On Tue, Aug 3, 2010 at 9:56 PM, Scott Newton <Scott.Newton (AT) integralgroup (DOT) co..nz<mailto:Scott.Newton (AT) integralgroup (DOT) co.nz>> wrote:
Scenario: Client has a primary server and an RSS server and the primary goes down. The RSS server is changed to standard to allow clients to continue to connect.

Is there a way of bring up the old primary and revert the new primary back to an RSS server without major interruptions to the client connections? I can do it by rebuilding the RSS server but I was wondering if there was a better way.

Thanks

--
Regards
Scott Newton
R&D Solutions Specialist

< Integral >< Axon >

DDI: +64 09 302 2788
Fax: +64 09 523 8810

Axon House, 414-422 Khyber Pass Road, Newmarket 1023, Auckland
PO Box 9824, Newmarket 1023, Auckland

This correspondence is confidential, is intended for the named recipient(s)only, and may contain information that is confidential or subject to legalprofessional privilege. If you are not the intended recipient you must notuse, disclose, distribute, copy or retain it. If you have received it in error please immediately notify me by return email and delete the emails. Thank you.
_______________________________________________
Informix-list mailing list
Informix-list (AT) iiug (DOT) org<ma...iiug (DOT) org>
http://www.iiug.org/mailman/listinfo/informix-list