|
|
Sponsored Content
Operating Systems
AIX
upgrade hacmp
Post 302484792 by shockneck on Monday 3rd of January 2011 08:40:01 AM
01-03-2011
Quote:
So just some thoughts in advance...By going from 5.4 to 6.1 you upgrade the version. So there might be more to consider than if you would just upgrade the release. It is almost impossible to foresee what might happen at what stage. E.g. do you upgrade RSCT also and if yes, how does upgrading RSCT work out? So to really know what is going to happen this has to be tested in a testing environment. If you can test, a rolling migration might be your choice.
In case you cannot test the upgrade with clones I would not use any online migration method offered by IBM but recreate the cluster. This is not as much work as it sounds. You can use either snapshot or (if IBM did not change the XML files from 5.4 to 6.1 again) online planning worksheet. Both methods keep the cluster definition so after installing the necessary software packages recreation of the cluster itself should not last langer than about 60 seconds. From my personal experiences this always works as long as there are no configuration errors (logical glitches, reservation probs, violation of networking rules, changes with snmp to name a few). So I would create snapshot and OLPW file from cluster. Uninstall HA software, install HA Software. Reboot. Check storage and network. Recreate Cluster from (convertet) snapshot or OLPW whichever suits you more.
Also remember that you can use alt_disk_install to keep the current setup for easy/fast rollback. Needless to say that you do make a backup of every cluster node before you start.
This User Gave Thanks to shockneck For This Post:
|
|
8 More Discussions You Might Find Interesting
1. AIX
Anyone ever did the upgrade before from 5.1? Any tips? (0 Replies)
Discussion started by: adiriot
0 Replies
3. AIX
Hi All,
My company is going to upgrade the db2 on the one node hacmp, I think there's one backup.
After the upgrade of the db2. Do I need to restart cluster and server? I mean, do a graceful shutdown of the cluster, reboot the server and do a cluster start. Is that it? Do I need to reboot... (1 Reply)
Discussion started by: itik
1 Replies
4. AIX
Hi,
Can we use network for heartbeat, I mean can we use different network card for heartbeat. (6 Replies)
Discussion started by: vjm
6 Replies
5. AIX
hi
can anyone explain the concepts of HACMP and configuration (step by step) (2 Replies)
Discussion started by: udtyuvaraj
2 Replies
6. AIX
Hi
What is the procedure to upgrade the MQ from 6 to 7 in aix hacmp cluster. Do i need to bring down the cluster
services running in both the nodes and then give #smitty installp in both the nodes separately. Please assist... (0 Replies)
Discussion started by: samsungsamsung
0 Replies
7. AIX
hi,
when I do a failover, hacmp always starts db2 but recently it fails to start db2..noticed the issue is db2nodes.cfg is not modified by hacmp and is still showing primary node..manually changed the node name to secondary after which db2 started immediately..unable to figure out why hacmp is... (4 Replies)
Discussion started by: gkr747
4 Replies
8. AIX
Hello,
I did offline HACMP(PowerHA) upgrade 5.4.1 to 5.5 - basically stopped HACMP services and upgraded cluster.* filesets.
Tried to start services again - topsvcs refused to start on second node complaining that node instance numbers are different - and indeed they are different.
This is... (2 Replies)
Discussion started by: vilius
2 Replies
LEARN ABOUT XFREE86
dh_systemd_start
DH_SYSTEMD_START(1) Debhelper DH_SYSTEMD_START(1) NAME dh_systemd_start - start/stop/restart systemd unit files SYNOPSIS dh_systemd_start [debhelperoptions] [--restart-after-upgrade] [--no-stop-on-upgrade] [unitfile...] DESCRIPTION dh_systemd_start is a debhelper program that is responsible for starting/stopping or restarting systemd unit files in case no corresponding sysv init script is available. As with dh_installinit, the unit file is stopped before upgrades and started afterwards (unless --restart-after-upgrade is specified, in which case it will only be restarted after the upgrade). This logic is not used when there is a corresponding SysV init script because invoke-rc.d performs the stop/start/restart in that case. OPTIONS --restart-after-upgrade Do not stop the unit file until after the package upgrade has been completed. This is the default behaviour in compat 10. In earlier compat levels the default was to stop the unit file in the prerm, and start it again in the postinst. This can be useful for daemons that should not have a possibly long downtime during upgrade. But you should make sure that the daemon will not get confused by the package being upgraded while it's running before using this option. --no-restart-after-upgrade Undo a previous --restart-after-upgrade (or the default of compat 10). If no other options are given, this will cause the service to be stopped in the prerm script and started again in the postinst script. -r, --no-stop-on-upgrade, --no-restart-on-upgrade Do not stop service on upgrade. --no-start Do not start the unit file after upgrades and after initial installation (the latter is only relevant for services without a corresponding init script). NOTES Note that this command is not idempotent. dh_prep(1) should be called between invocations of this command (with the same arguments). Otherwise, it may cause multiple instances of the same text to be added to maintainer scripts. Note that dh_systemd_start should be run after dh_installinit so that it can detect corresponding SysV init scripts. The default sequence in dh does the right thing, this note is only relevant when you are calling dh_systemd_start manually. SEE ALSO debhelper(7) AUTHORS pkg-systemd-maintainers@lists.alioth.debian.org 11.1.6ubuntu2 2018-05-10 DH_SYSTEMD_START(1)