Scribd
Upload
25 views

Migrations: RPM - Prefix /opt/ (Newbuild Dir) - Ivh .RPM

The document discusses 3 types of MQ migrations: 1) Parallel-to-parallel migration which installs an upgraded version on the same server without disrupting the current version. 2) Version-to-version migration which removes the existing version and installs a newer one. 3) Server-to-server migration which moves QMs and data from one server to another by taking backups, uploading them to the new server, recreating the QMs, and importing the backups.

Uploaded by

Ravi Ghantasala
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
25 views

Migrations: RPM - Prefix /opt/ (Newbuild Dir) - Ivh .RPM

The document discusses 3 types of MQ migrations: 1) Parallel-to-parallel migration which installs an upgraded version on the same server without disrupting the current version. 2) Version-to-version migration which removes the existing version and installs a newer one. 3) Server-to-server migration which moves QMs and data from one server to another by taking backups, uploading them to the new server, recreating the QMs, and importing the backups.

Uploaded by

Ravi Ghantasala
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

MIGRATIONS

We have 3 kinds of migrations in MQ.


1. Parallel – to – parallel (which is also called as side by side)
2. Version - to - version
3. Server – to – server
Parallel migration : without disturbing the current version, we can install the
upgraded version in the same server is called parallel migration.
As already we have one build in the server, if we try to install the new build in
the same path, it will throw conflict error.
So to avoid that, the user define path can be given like,

rpm –prefix /opt/(newbuild dir) -ivh *.rpm

To work in the newly installed version, we have to set it as primary.


Before that, have to remove the previous version from primary setup, And now
set newly installed build as primary.
./setmqinst -x -p installation_path (unset old version from primary)
./setmqinst -I -p installation_path (set new version sa primary)

to chk installation path,


dspmq -o installation.
To chk how many versions,
Dspmqver -i
Version – to – version

Removing the existing version and installing the newer version is called as
Version- To – Version migration.
Whenever we remove the existing MQ s/w, only the /opt/mqm will be
removed. But the /var/mqm log files(QMs etc) will not be removed.
After installing newer version , the /var/mqm logs of the removed version will
be automatically run on the newer version.

Difference b/n paraller & version migration:

The main advantage of parallel migration is DOWN TIME.


i.e. in version migration, to install the new version we have to shutdown the
QM in the older version and it has to be in the down mode till the new version
will get installed.
Where as, in parallel we don’t need to shutdown the QMs to install the
another version.
Mostly we use version- to versio only, but if there are any high criticality QMs
are there, then we use parallel migration.
Server – to -server

Migrating QMs from one server to another server is called as server-to-server


migration.

To move the QMs and other data from one server to another server,
 Firstly, we need to take the backups like(QMGR backup, authentication
backup etc)
 We will save all these backups in one folder and by using winscp we will
upload this folder to the another server environment.
 And in the another server, we have to create the QMs with same and
with same config as shown in the qm.ini file of previous server.
 Now import the QMGR backup files by
Runmqsc QMame < /path/foldername/filename.txt
 Import authentications backup,
Cd /path/folder
./QMname_auth.sh

You might also like