User`s guide

16
Upgrading Nodes in Clusters
Upgrading Nodes in a Failover Cluster
The process of upgrading nodes in a failover cluster includes the following steps:
1 Upgrading active nodes in the cluster.
2 Upgrading passive nodes in the cluster.
Important! Upgrade one cluster node at a time. Upgrading more than one node simultaneously is
not supported and may damage your systems.
Checking Clustered Services
Each active node must be upgraded together with the clustered service running on it. So before
starting the upgrade procedure, make sure that you know which clustered service is running on
which node. To see the list of clustered services and the nodes where they are running, run this
command on any of your cluster nodes:
# clustat
Service Name Owner (Last) State
------- ---- ----- ------ -----
service:vz-0 server1.com started
service:vz-1 server2.com started
Once you upgrade all active nodes in the cluster, no clustered services must be left un-upgraded.
Upgrading Active Nodes in the Cluster
First, you need to upgrade all active nodes in the failover cluster. To upgrade an active node, do the
following:
1 Freeze the clustered service running on the active node:
# clusvcadm -Z clustered_service_name
(where clustered_service_name is the name of the clustered service)
If your version of clusvcadm does not support the -Z option, use the -l option instead. This
option prevents the specified clustered service from running on a local node (that is, on the
node where you run the command). If you use the -l option, execute the command on all
cluster nodes (both active and passive), except for the node you are upgrading.
2 Open the /etc/fstab file on the node for editing, and add the /vz entry to it. Make sure you
add the right /vz entry to the file:
a Run the clustat utility to find out the name of the clustered service running on the active
node.
b Search the cluster configuration file (/etc/cluster/cluster.conf) for the UUID of the
device associated with the clustered service, for example:
# cat /etc/cluster/cluster.conf
...