Novell BUSINESS CONTINUITY CLUSTERING 1.1 SP2 - ADMINISTRATION, Administration Manual

Page: 56 / 142

56 BCC 1.1 SP2: Administration Guide for NetWare 6.5 SP8
no
vd
ocx
(e
n)
13
Ma
y 20
09
5.1.2 Performing a Rolling Cluster Upgrade
Performing a rolling upgrade of NetWare and applying the latest patches lets you keep your cluster
up and running and lets your users continue to access the network while the upgrade is being
performed.
For example, during a rolling cluster upgrade, one server is upgraded from NetWare SP6 to SP8 and
the latest patches are applied while the other servers in the cluster continue running a previous
support pack of NetWare 6.5. Then another server is upgraded and patched, and then another, until
all servers in the cluster have been upgraded to NetWare 6.5 SP8 with the latest patches.
After upgrading NetWare and applying the latest patches, reboot the server to automatically load
Cluster Services software.
During the upgrade process, cluster pools, volumes, and resources fail over from the server being
upgraded to other servers in the cluster. After a cluster server is upgraded and brought back online,
the pools, volumes, and resources that failed over to other servers in the cluster during the upgrade
process fail back to the upgraded server.
5.2 Disabling BCC 1.0, Upgrading Servers to
NetWare 6.5 SP8, then Enabling BCC 1.1 SP2
The safest and most straightforward way for you to upgrade from BCC 1.0 to BCC 1.1 SP2 is to
disable BCC on the peer clusters, upgrade to NetWare 6.5 SP8, re-install BCC 1.1 SP2, and re-
configure BCC for the clusters.
This approach leaves you without the BCC capability during the upgrade; however, the clustering
high availability is still active.
1 Create a worksheet for the Identity Manager driver configuration for each peer cluster where
you note the ports, landing zones, BCC drivers and driver sets, and certificates that are
currently in use.
You can use this information later when you re-create the drivers.
2
Stop the BCC drivers from running on the Identity Manager nodes of every peer cluster.
3 On the Identity Manager node in each peer cluster, delete the Identity Manager drivers and
driver sets for the cluster.
4 Disable BCC for each of the cluster resources on all nodes in every peer cluster.
5 Disable BCC for each peer cluster.
6 Clean up the landing zones in each peer cluster.
7 Uninstall BCC 1.0 from each node in every peer cluster.
8 Perform a rolling cluster upgrade for all nodes in a peer cluster:
8a Issue the
cluster leave
command on one node in the cluster.
8b Update NetWare 6.5 from version SP5 or SP6 to version SP8, and apply the latest patches
for NetWare and Novell Cluster Services.
For information, see the
NetWare Installation Guide (http://www.novell.com/
documentation/oes2/inst_oes_nw/data/b7211uh.html)
8c Issue the
cluster join
command on the node.
8d Install BCC 1.1 SP2 on each node in the cluster. Do not start BCC at this time.