|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Upgrade from MBV6 to MBV7 |
« View previous topic :: View next topic » |
Author |
Message
|
satya kolli |
Posted: Sun Jun 06, 2010 5:48 am Post subject: Upgrade from MBV6 to MBV7 |
|
|
Novice
Joined: 16 May 2010 Posts: 11
|
Hi,
Do we need to take back up of the broker DB2 while upgrading from MBV6 to MBV7? because in MBV7 broker doesn't require a DB2, how the broker takes its DB2 data transactions from the DB2 to its newer version MBV7 while up gradation and where it stores the data after up gradation?
does this command do everything mqsimigratecomponents <BrokerName>?
can any one help me here? |
|
Back to top |
|
 |
exerk |
Posted: Sun Jun 06, 2010 6:08 am Post subject: |
|
|
 Jedi Council
Joined: 02 Nov 2006 Posts: 6339
|
Yes...my bit of help will be to move this to a more appropriate forum, i.e. the Broker forum  _________________ It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
Back to top |
|
 |
smdavies99 |
Posted: Sun Jun 06, 2010 12:27 pm Post subject: Re: Upgrade from MBV6 to MBV7 |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
satya kolli wrote: |
Hi,
Do we need to take back up of the broker DB2 while upgrading from MBV6 to MBV7? because in MBV7 broker doesn't require a DB2, how the broker takes its DB2 data transactions from the DB2 to its newer version MBV7 while up gradation and where it stores the data after up gradation?
does this command do everything mqsimigratecomponents <BrokerName>?
|
Have you read the V7 documentation especially the relevant sections about migration from V6.x to V7.0?
There is a lot of useful information there.
If I were you, I'd setup a trial system (probably in a VM) and try it all out.
In the one system I've worked on that is well advanced with this operation is not going to migrate. They are going to build a clean V7 system and then run int alongside the V6.1 one and gradually move the flows etc over.
This is all after testing everything again with the new broker software.
IMHO, with the removal of the configmgr, you are going to have to make changes to your broker access control anyway so I think the clean approach is the safest. Then you can take one step at a time. _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
Back to top |
|
 |
satya kolli |
Posted: Sun Jun 06, 2010 9:54 pm Post subject: |
|
|
Novice
Joined: 16 May 2010 Posts: 11
|
Yes, I've gone through the doc (Message Broker mogration to MBV7) I couldn't get the proper info before i start... let me check in VMware.. then I'll proceed further...
Thank a lot for your info.  |
|
Back to top |
|
 |
mqmatt |
Posted: Mon Jun 07, 2010 1:45 pm Post subject: |
|
|
 Grand Master
Joined: 04 Aug 2004 Posts: 1213 Location: Hursley, UK
|
The mqsimigratecomponents command will take everything in your system database and copy it onto the filesystem; it doesn't write or delete anything in that system database, so there's no need to take an additional backup of it. |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|