Yvette,

I strongly recommend, to archive the directory "/var/mqm" before you upgrade. 
Then pou will be able to go back to V5.3 using the archive date. I would insert 
this step as a second entry into "phase 1" of Roger's list. 

Regards
Hubert


> -----Ursprüngliche Nachricht-----
> Von: MQSeries List <[email protected]>
> Gesendet: 04.10.06 09:01:53
> An: [email protected]
> Betreff: Re: MQ upgrade to V6.0.1.1 on AIX


> 
> Hi Roger
> 
> 
> I'll discuss this with our AIX admins.  This does look like the safer way of 
> doing things and conducive to warm fuzzy feelings during the upgrade.  
> 
> 
> Thanks very much for the input.
> 
> 
> Kind regards
> 
> Yvette
> 
> 
> -----Original Message-----
> 
> From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of Roger Lacroix
> 
> Sent: 03 October 2006 07:47 PM
> 
> To: [email protected]
> 
> Subject: Re: MQ upgrade to V6.0.1.1 on AIX
> 
> 
> Hi,
> 
> 
> > My questions are what is updated in the /var/mqm directory and what 
> 
> > would the effect be when the second server is made active, still 
> 
> > running V5.3, reading what is potentially a V6.0.1.1 /var/mqm 
> 
> > directory?  Will this cause any issues with our upgrade?
> 
> 
> I'm guessing you are running in the standard HA configuration of 
> Active/Passive?
> 
> 
> I would mostly certainly not try to start a v5.3 QMgr with data that was from 
> an upgrade of v6.0.  I would bet my truck that things would break or at least 
> get corrupted.
> 
> 
> Here's what I would do:
> 
> 
> - Stop all running QMgrs on the HA servers.
> 
> - Take the HA offline.
> 
> 
> Phase 1:
> 
> - Bring ONLY the mount points online on server 'A'
> 
> - Upgrade MQ to v6
> 
> - Freeze the QMgrs to server 'A'  (Veritas terminology)
> 
> - Start the QMgrs on server 'A'
> 
> - Test the QMgrs
> 
> - Stop all running QMgrs on the HA servers.
> 
> - Take the HA offline.
> 
> 
> Phase 2:
> 
> - Bring ONLY the mount points online on server 'B'
> 
> - Upgrade MQ to v6
> 
> - Freeze the QMgrs to server 'B'  (Veritas terminology)
> 
> - Start the QMgrs on server 'B'
> 
> - Test the QMgrs
> 
> - Stop all running QMgrs on the HA servers.
> 
> - Take the HA offline.
> 
> 
> Phase 3:
> 
> - Bring up the HA and QMgr on server 'A'
> 
> - Test the QMgrs
> 
> - Failover to the other server 'B'
> 
> - Test the QMgrs
> 
> - Failover back to the primary server 'A'
> 
> 
> Give the big thumbs up and everything worked.
> 
> 
> 
> Regards,
> 
> Roger Lacroix
> 
> Capitalware Inc.
> 
> http://www.capitalware.biz
> 
> 
> 
> 
> Quoting "Carroll, Y. (Yvette)" <[EMAIL PROTECTED]>:
> 
> 
> > Hi all
> 
> >
> 
> > We're about to start our prod upgrades to V6.0.1.1 on AIX.  In prod we 
> 
> > have several HACMP servers but we don't have any in any of our other 
> 
> > environments so we've had no opportunity to practice such an upgrade.
> 
> >
> 
> > I've looked in the manuals but can't find the answer to a question re 
> 
> > the file system during the upgrade:
> 
> > We've got the software on each of the two servers in the HACMP cluster 
> 
> > (don't know if that's the right term) and the /var/mqm directory on a 
> 
> > shared disk visible to the active server.  During the upgrade, we were 
> 
> > planning to first upgrade the standby box and then swap it to active 
> 
> > to test the install then do the same for the new standby box.
> 
> > My questions are what is updated in the /var/mqm directory and what 
> 
> > would the effect be when the second server is made active, still 
> 
> > running V5.3, reading what is potentially a V6.0.1.1 /var/mqm 
> 
> > directory?  Will this cause any issues with our upgrade?
> 
> >
> 
> > Thanks!
> 
> >
> 
> > Kind regards
> 
> > Yvette Carroll
> 
> > Nedbank Ltd.
> 
> > Database and Middleware support - MQ support specialist
> 
> >
> 
> > +27 83 644 0608 (cell)
> 
> > +27 11 500 3754 (w)
> 
> > +27 11 500 4331 (fax)
> 
> >
> 
> >
> 
> > ********************
> 
> > Nedbank Limited Reg No 1951/000009/06. The following link displays   
> 
> > the names of the Nedbank Board of Directors and Company Secretary. [  
> 
> > http://www.nedbank.co.za/terms/DirectorsNedbank.htm ]
> 
> > This email is confidential and is intended for the addressee only.   
> 
> > The following link will take you to Nedbank's legal notice. [   
> 
> > http://www.nedbank.co.za/terms/EmailDisclaimer.htm ]
> 
> > ********************
> 
> >
> 
> > To unsubscribe, write to [EMAIL PROTECTED] and, in 
> 
> > the message body (not the subject), write: SIGNOFF MQSERIES 
> 
> > Instructions for managing your mailing list subscription are provided 
> 
> > in the Listserv General Users Guide available at http://www.lsoft.com
> 
> > Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
> 
> >
> 
> 
> To unsubscribe, write to [EMAIL PROTECTED] and, in the message body (not the 
> subject), write: SIGNOFF MQSERIES Instructions for managing your mailing list 
> subscription are provided in the Listserv General Users Guide available at 
> http://www.lsoft.com
> 
> 
> Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
> 
> 
> -----------------------------------------------------------------
> 
> Nedbank Limited Reg No 1951/000009/06. The following link displays the names 
> of the Nedbank Board of Directors and Company Secretary.
> 
> This email is confidential and is intended for the addressee only. The 
> following link will take you to Nedbank's legal notice.
> 
> 
> -----------------------------------------------------------------
> 

-- 
Hubert Kleinmanns
Beratung / Schulung / Projektleitung

Tel.: +49 (0) 60 78 / 7 12 21
Fax: +49 (0) 60 78 / 7 12 25
Mobil: +49 (0) 178 / 6 97 22 54

To unsubscribe, write to [EMAIL PROTECTED] and,
in the message body (not the subject), write: SIGNOFF MQSERIES
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html

Reply via email to