change server's

Greetings to the list, we now have in the company Informix 10.x HDR on AIX 5.x * The primary server is a pSeries 510 and is in the seat A * The server side is a pSeries 570 and east on the seat B (5000 km) * The HDR is done by Internet 1MB My query is as follows: * I want to change the primary server pSeries 510 with a new pSeries 570 server without breaking with the HDR. I would appreciate can send suggestions. Greetings _________________________________________________________________

I don't think you can do it without a little downtime, and some breaking of HDR. Assuming you don't want to run the live service the the old p570 for any length of time here's how I'd do it: - Implement the new p570 - Restore a backup of the live database to the new p570 with ontape -p - break HDR between the p510 and the old p570 - establish HDR between the p510 and the new p570 - reverse the direction of HDR so that the new p570 becomes the primary and the p510 becomes the secondary - shutdown the p510 - change the sqlhosts on the old HDR to tell it that the primary Informix service is now on the new p570 and bring it up Should be just one live downtime, plus some periods when HDR is inactive. Might be easier in IDS 11 with RSS; I don't know.

You 'might' be able to do it online. - Reverse the HDR pair, so the primary is now the old p570. - shut down the p510 - Copy all of the database chunks across (rootdbs, dataspaces, blobspaces, external tablespaces, everything) to the new p570 server along with the configuration files and Informix binaries etc - Set the new p570 server to the same IP address as the old p510 - Start the engine on the p570 - should come up as the HDR secondary to the old p570 and run logs to catch up. - Reverse the HDR pair again. This will work as long as the database engine doesn't think it has moved. The IP address, ports, hostname will all have to be the same. Neil's answer is far cleaner than my suggestion, but if you can't stand downtime it should work. And yes, under 11 you could bring the new p570 up as an RSS, then promote it to an HDR secondary then to the primary. Jarrod Teale Fonterra New Zealand -----Original Message----- From: informix-list-bounces@iiug.org [mailto:informix-list-bounces@iiug.org] On Behalf Of Neil Truby Sent: Sunday, 9 November 2008 3:14 p.m. To: informix-list@iiug.org Subject: Re: change server's I don't think you can do it without a little downtime, and some breaking of HDR. Assuming you don't want to run the live service the the old p570 for any length of time here's how I'd do it: - Implement the new p570 - Restore a backup of the live database to the new p570 with ontape -p - break HDR between the p510 and the old p570 - establish HDR between the p510 and the new p570 - reverse the direction of HDR so that the new p570 becomes the primary and the p510 becomes the secondary - shutdown the p510 - change the sqlhosts on the old HDR to tell it that the primary Informix service is now on the new p570 and bring it up Should be just one live downtime, plus some periods when HDR is inactive. Might be easier in IDS 11 with RSS; I don't know. _______________________________________________ Informix-list mailing list Informix-list@iiug.org http://www.iiug.org/mailman/listinfo/informix-list DISCLAIMER: This email contains confidential information and may be legally privileged. If you are not the intended recipient or have received this email in error, please notify the sender immediately and destroy this email. You may not use, disclose or copy this email or its attachments in any way. Any opinions expressed in this email are those of the author and are not necessarily those of the Fonterra Co-operative Group. http://www.fonterra.com/

"Jarrod Teale" <Jarrod.Teale@fonterra.com> wrote in message news:mailman.302.1226258661.874.informix-list@iiug.org... You 'might' be able to do it online. >> - Reverse the HDR pair, so the primary is now the old p570. - shut down the p510 - Copy all of the database chunks across (rootdbs, dataspaces, blobspaces, external tablespaces, everything) to the new p570 server along with the configuration files and Informix binaries etc - Set the new p570 server to the same IP address as the old p510 - Start the engine on the p570 - should come up as the HDR secondary to the old p570 and run logs to catch up. - Reverse the HDR pair again. This will work as long as the database engine doesn't think it has >> moved. The IP address, ports, hostname will all have to be the same. >> Neil's answer is far cleaner than my suggestion, Why, thank you <blush> >> ... but if you can't stand downtime [mine] should work. I don't understand how yours avoid downtime, as there will be some on each occasion that you reverse HDR. >> And yes, under 11 you could bring the new p570 up as an RSS, then promote >> it to an HDR secondary then to the primary. Thought so, but I don't have any customers on 11 yet :-( Fonterra New Zealand -----Original Message----- From: informix-list-bounces@iiug.org [mailto:informix-list-bounces@iiug.org] On Behalf Of Neil Truby Sent: Sunday, 9 November 2008 3:14 p.m. To: informix-list@iiug.org Subject: Re: change server's I don't think you can do it without a little downtime, and some breaking of HDR. Assuming you don't want to run the live service the the old p570 for any length of time here's how I'd do it: - Implement the new p570 - Restore a backup of the live database to the new p570 with ontape -p - break HDR between the p510 and the old p570 - establish HDR between the p510 and the new p570 - reverse the direction of HDR so that the new p570 becomes the primary and the p510 becomes the secondary - shutdown the p510 - change the sqlhosts on the old HDR to tell it that the primary Informix service is now on the new p570 and bring it up Should be just one live downtime, plus some periods when HDR is inactive. Might be easier in IDS 11 with RSS; I don't know. _______________________________________________ Informix-list mailing list Informix-list@iiug.org http://www.iiug.org/mailman/listinfo/informix-list DISCLAIMER: This email contains confidential information and may be legally privileged. If you are not the intended recipient or have received this email in error, please notify the sender immediately and destroy this email. You may not use, disclose or copy this email or its attachments in any way. Any opinions expressed in this email are those of the author and are not necessarily those of the Fonterra Co-operative Group. http://www.fonterra.com/

If DR_AUTO is set to auto failover (1 I think) the secondary will become a standard engine , you could do this whole process without having both systems offline at the same time. I never used the DR_AUTO flag, but those at the IOD this year assured me that it works. Of course with a version 10 engine, all of the clients will have to be manually redirected to the alternate server - no connection manager :( -----Original Message----- From: informix-list-bounces@iiug.org [mailto:informix-list-bounces@iiug.org] On Behalf Of Neil Truby Sent: Monday, 10 November 2008 10:05 a.m. To: informix-list@iiug.org Subject: Re: change server's "Jarrod Teale" <Jarrod.Teale@fonterra.com> wrote in message news:mailman.302.1226258661.874.informix-list@iiug.org... You 'might' be able to do it online. >> - Reverse the HDR pair, so the primary is now the old p570. - shut down the p510 - Copy all of the database chunks across (rootdbs, dataspaces, blobspaces, external tablespaces, everything) to the new p570 server along with the configuration files and Informix binaries etc - Set the new p570 server to the same IP address as the old p510 - Start the engine on the p570 - should come up as the HDR secondary to the old p570 and run logs to catch up. - Reverse the HDR pair again. This will work as long as the database engine doesn't think it has >> moved. The IP address, ports, hostname will all have to be the same. >> Neil's answer is far cleaner than my suggestion, Why, thank you <blush> >> ... but if you can't stand downtime [mine] should work. I don't understand how yours avoid downtime, as there will be some on each occasion that you reverse HDR. >> And yes, under 11 you could bring the new p570 up as an RSS, then >> promote it to an HDR secondary then to the primary. Thought so, but I don't have any customers on 11 yet :-( Fonterra New Zealand -----Original Message----- From: informix-list-bounces@iiug.org [mailto:informix-list-bounces@iiug.org] On Behalf Of Neil Truby Sent: Sunday, 9 November 2008 3:14 p.m. To: informix-list@iiug.org Subject: Re: change server's I don't think you can do it without a little downtime, and some breaking of HDR. Assuming you don't want to run the live service the the old p570 for any length of time here's how I'd do it: - Implement the new p570 - Restore a backup of the live database to the new p570 with ontape -p - break HDR between the p510 and the old p570 - establish HDR between the p510 and the new p570 - reverse the direction of HDR so that the new p570 becomes the primary and the p510 becomes the secondary - shutdown the p510 - change the sqlhosts on the old HDR to tell it that the primary Informix service is now on the new p570 and bring it up Should be just one live downtime, plus some periods when HDR is inactive. Might be easier in IDS 11 with RSS; I don't know. _______________________________________________ Informix-list mailing list Informix-list@iiug.org http://www.iiug.org/mailman/listinfo/informix-list DISCLAIMER: This email contains confidential information and may be legally privileged. If you are not the intended recipient or have received this email in error, please notify the sender immediately and destroy this email. You may not use, disclose or copy this email or its attachments in any way. Any opinions expressed in this email are those of the author and are not necessarily those of the Fonterra Co-operative Group. http://www.fonterra.com/ _______________________________________________ Informix-list mailing list Informix-list@iiug.org http://www.iiug.org/mailman/listinfo/informix-list DISCLAIMER: This email contains confidential information and may be legally privileged. If you are not the intended recipient or have received this email in error, please notify the sender immediately and destroy this email. You may not use, disclose or copy this email or its attachments in any way. Any opinions expressed in this email are those of the author and are not necessarily those of the Fonterra Co-operative Group. http://www.fonterra.com/