[go: up one dir, main page]
Scribd
Upload
14 views2 pages

MQ Linux

The document outlines a pre-checklist and patching procedure for managing a server running MQ services, including server uptime checks, taking backups, and verifying database connectivity. It details commands for checking system status, extracting and installing binaries, and ensuring application team coordination for service deployment. A rollback plan is also provided, which includes taking backups and removing maintenance updates if necessary.

Uploaded by

prashantrajak474
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as ODT, PDF, TXT or read online on Scribd
14 views2 pages

MQ Linux

The document outlines a pre-checklist and patching procedure for managing a server running MQ services, including server uptime checks, taking backups, and verifying database connectivity. It details commands for checking system status, extracting and installing binaries, and ensuring application team coordination for service deployment. A rollback plan is also provided, which includes taking backups and removing maintenance updates if necessary.

Uploaded by

prashantrajak474
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as ODT, PDF, TXT or read online on Scribd
You are on page 1/ 2

Pre Checklist

after cyberark approval immediately check for uptime of server , if server is up more than 30 days, We
will ask for reboot of server.

Take VM backup.

Ask application team for DB port and DB IP


telnet DB_IP DB_portno
ps -ef | grep mqm - To check MQ related services.
Dspmq - To Check Queue Manager status.
hostname - display hostname
uname - display OS
ifconfig -a - display ip detail
df -h - display space detail in GB
netstat -an - display socket used by process
top - display the process, Load & CPU & Memory of MQ
uptime - if server is up more than 30 days, We will ask for reboot of server.

/usr/<MQ Base>/bin/$ dspmqver -i – To display version and instances of MQ.

Copy binaries from local system to server.

Take backup of /opt/mqm and /var/mqm directory.


tar -cvzf backupname.tar <backup file> - tar command

OR

tar cvf - <backupfile> | gzip > backupname.tar.gz - tar+gzip command

Patching

<Binary_path_location>/ - Extract the binary file


<Binary_path_location>/ Install - rpm -ivh <package name.rpm.>

ps -ef | grep mqm - To check MQ related services.


Dspmq - To Check Queue Manager status.
hostname - display hostname
uname - display OS
ifconfig -a - display ip detail
df -h - display space detail in GB
netstat -an - display socket used by process
topas - display the process, Load & CPU & Memory of MQ
Ask application team for the sanity and ask them to start the required services, deployments and
connectivity with Database.
After service up we need to check /var/mqm/logs. – all logs generates in this path.
Rollback Plan

Take backup.

Remove mainetnance level updates

<Binary_Path_Location>/ rpm -ev 'rpm -qa | grep MQSeries | grep "<Fixpack version>".

You might also like