![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
From:, Tom Lehr <tomcaml (AT) gmail (DOT) com To: informix-list (AT) iiug (DOT) org Date: 04/19/2010 02:20 PM Subject: version 11 in plae upgrade and HDR Sent by: informix-list-bounces (AT) iiug (DOT) org Hello All This is a RTFM manual question, I know, but I am going to put this out there anyway, especially since I think all of our upgrades in the past have been new hardware migrations and I want to be sure as there was some doubt in house . In the v11 Info Center, under "Migrating Clusters to a New Release", #17 states: If you have an HDR secondary server: a. Reestablish the pair on the primary by issuing onmode -d primary "hdr_secondary_name" b. Start the HDR secondary server with level 0 restore from level 0 backup that was made on the primary after migration. c. On the secondary, run onmode -d secondary "primary_server_name" , and wait for 'hdr secondary operational' in the message log. I am reading that this states to completely have the secondary server redone through the use of a level 0 backup of primary being applied as a restore on the secondary - correct? and by stating to reestablish the pair, they just mean to run the command on primary and then wait for the restore to finish on the secondary server and then run the next onmode -d. Thanks Tom _______________________________________________ Informix-list mailing list Informix-list (AT) iiug (DOT) org http://www.iiug.org/mailman/listinfo/informix-list |
#3
| |||
| |||
|
|
That's correct -- after the successful migration of the primary instance, you need to re-create the HDR secondary instance. - Nilesh - informix-list-boun... (AT) iiug (DOT) org wrote on 04/19/2010 02:18:39 PM: From:, Tom Lehr <tomc... (AT) gmail (DOT) com To: informix-l... (AT) iiug (DOT) org Date: 04/19/2010 02:20 PM Subject: version 11 in plae upgrade and HDR Sent by: informix-list-boun... (AT) iiug (DOT) org Hello All This is a *RTFM manual question, I know, but I am going to put this out there anyway, especially since I think all of our upgrades in the past have been new hardware migrations and I want to be sure as there was some doubt in house . In the v11 Info Center, under "Migrating Clusters to a New Release", #17 states: If you have an HDR secondary server: * a. Reestablish the pair on the primary by issuing onmode -d primary "hdr_secondary_name" * b. Start the HDR secondary server with level 0 restore from level 0 backup that was made on the primary after * *migration. * c. On the secondary, run onmode -d secondary "primary_server_name" , and wait for 'hdr secondary operational' in the message log. I am reading that this states to completely have the secondary server redone through the use of a level 0 backup of primary being applied as a restore on the secondary *- correct? and by stating to reestablish the pair, they just mean to run the command on primary and then wait for the restore to finish on the secondary server and then run the next onmode -d. Thanks Tom _______________________________________________ Informix-list mailing list Informix-l... (AT) iiug (DOT) org http://www.iiug.org/mailman/listinfo/informix-list- Hide quoted text - - Show quoted text - |
#4
| |||
| |||
|
|
"Nilesh Ozarkar" <nilesho (AT) us (DOT) ibm.com> wrote in message news:mailman.137.1271708759.1071.informix-list (AT) iiug (DOT) org... That's correct -- after the successful migration of the primary instance, |
#5
| |||
| |||
|
|
"Nilesh Ozarkar" <nile... (AT) us (DOT) ibm.com> wrote in message news:mailman.137.1271708759.1071.informix-list (AT) iiug (DOT) org... That's correct -- after the successful migration of the primary instance, you need to re-create the HDR secondary instance. I can confirm this. *It is actually preventing one of our customers from ugrading from 10, as HDR is being run over such a vast distance that it would not be viable to re-establish it now, given the data growth :-( |
#6
| |||
| |||
|
|
Thanks Neil I will quiz folks more for other gotchya's at the IIUG conference in KC but for now I am working hard to convince others around me that this is just how the thing is supposed to work and be done, etc. for the in place wiith HDR going from v10 to v11. Some thoughts were that it was as simple as changing primary and then secondary catches up to it to complete the migration but i know the logs don't send that kind of internal information, etc - which is why I am assuming all that re-do is necessary. Tom On Apr 19, 5:21 pm, "Neil Truby" <neil.tr... (AT) ardenta (DOT) com> wrote: "Nilesh Ozarkar" <nile... (AT) us (DOT) ibm.com> wrote in message news:mailman.137.1271708759.1071.informix-list (AT) iiug (DOT) org... That's correct -- after the successful migration of the primary instance, you need to re-create the HDR secondary instance. I can confirm this. It is actually preventing one of our customers from ugrading from 10, as HDR is being run over such a vast distance that it would not be viable to re-establish it now, given the data growth :-( _______________________________________________ Informix-list mailing list Informix-list (AT) iiug (DOT) org http://www.iiug.org/mailman/listinfo/informix-list |
#7
| |||
| |||
|
|
This is totally unsupported; but we managed to upgrade from 10.0.fc6 to 11.10.fc1 about 6 months ago in a similar situation (wide-area hdr, database too big to archive/restore over the network). Here's what we did:- * *- All threads off, take both engines to quiescent mode * *- Shutdown primary; onmode -yuck * *- Shutdown secondary; onmode -yk * *- Get the new Informix software in place on both servers (we have * *$INFORMIXDIR pointing to a symbolic link so we can upgrade easily) * *- Bring up the primary -- allow all upgrade activity to complete * *- Bring up the secondary --- internal upgrade processes + updated pages * *spooled through HDR appeared to perform the upgrade cleanly I'll repeat, IBM in no way sanctioned or supported upgrading the HDR pairin this manner; we did this out of desperation to get the upgrade completed. On 19 April 2010 23:57, Tom Lehr <tomc... (AT) gmail (DOT) com> wrote: Thanks Neil I will quiz folks more for other gotchya's at the IIUG conference in KC but for now I am working hard to convince others around me that this is just how the thing is supposed to work and be done, etc. for the in place wiith HDR going from v10 to v11. Some thoughts were that it was as simple as changing primary and then secondary catches up to it to complete the migration but i know the logs don't send that kind of internal information, etc - which is why I am assuming all that re-do is necessary. Tom On Apr 19, 5:21 pm, "Neil Truby" <neil.tr... (AT) ardenta (DOT) com> wrote: "Nilesh Ozarkar" <nile... (AT) us (DOT) ibm.com> wrote in message news:mailman.137.1271708759.1071.informix-list (AT) iiug (DOT) org... That's correct -- after the successful migration of the primary instance, you need to re-create the HDR secondary instance. I can confirm this. *It is actually preventing one of our customersfrom ugrading from 10, as HDR is being run over such a vast distance that it would not be viable to re-establish it now, given the data growth :-( _______________________________________________ Informix-list mailing list Informix-l... (AT) iiug (DOT) org http://www.iiug.org/mailman/listinfo/informix-list -- Nick Lello | Web Architect o**************+44*(0)*20*7170*5200********+44*(0) *20*7170*5200| d**************+44*(0)*20*7170*5215********+44*(0) *20*7170*5215| m**************+44*(0)*7917*138319********+44*(0)* 7917*138319| nick.le... (AT) rentrak (DOT) com RENTRAK EDI |www.rentrak.com| NASDAQ: RENT Notice: On 29th January 2010, Rentrak Corporation acquired Nielsen EDI and, as such, this message may be delivered via Rentrak or Nielsen message systems. This message is confidential and is intended only for the recipient(s) named above. If you have received this message in error, or are not the named recipient(s), please immediately notify the sender and delete this message.- Hide quoted text - - Show quoted text - |
#8
| |||
| |||
|
|
Here's what we did:- |
|
I'll repeat, IBM in no way sanctioned or supported upgrading the HDR pair in this manner; we did this out of desperation to get the upgrade completed. |
#9
| |||
| |||
|
|
"Nick Lello" <nick.le... (AT) rentrakmail (DOT) com> wrote in message news:mailman.140.1271749880.1071.informix-list (AT) iiug (DOT) org... This is totally unsupported; but we managed to upgrade from 10.0.fc6 to 11.10.fc1 about 6 months ago in a similar situation (wide-area hdr, database too big to archive/restore over the network). Here's what we did:- All threads off, take both engines to quiescent mode Shutdown primary; onmode -yuck Shutdown secondary; onmode -yk Get the new Informix software in place on both servers (we have $INFORMIXDIR pointing to a symbolic link so we can upgrade easily) Bring up the primary -- allow all upgrade activity to complete Bring up the secondary --- internal upgrade processes + updated pages spooled through HDR appeared to perform the upgrade cleanly I'll repeat, IBM in no way sanctioned or supported upgrading the HDR pair in this manner; we did this out of desperation to get the upgrade completed. That's interesting. *In depsperation, we might need to do this too ... |
#10
| |||
| |||
|
|
"Nick Lello" <nick.le... (AT) rentrakmail (DOT) com> wrote in message news:mailman.140.1271749880.1071.informix-list (AT) iiug (DOT) org... This is totally unsupported; but we managed to upgrade from 10.0.fc6 to 11.10.fc1 about 6 months ago in a similar situation (wide-area hdr, database too big to archive/restore over the network). Here's what we did:- All threads off, take both engines to quiescent mode Shutdown primary; onmode -yuck Shutdown secondary; onmode -yk Get the new Informix software in place on both servers (we have $INFORMIXDIR pointing to a symbolic link so we can upgrade easily) Bring up the primary -- allow all upgrade activity to complete Bring up the secondary --- internal upgrade processes + updated pages spooled through HDR appeared to perform the upgrade cleanly I'll repeat, IBM in no way sanctioned or supported upgrading the HDR pair in this manner; we did this out of desperation to get the upgrade completed. That's interesting. In depsperation, we might need to do this too ... |
|
1. Create a third mirror for the primary at the secondary site (resync might take several days - fine) |
![]() |
| Thread Tools | |
| Display Modes | |
| |