Installing The Bcc Patch On A Fully Patched Oes 2 Sp2 Linux Bcc Cluster - Novell BUSINESS CONTINUITY CLUSTERING 1.2.1 - ADMINISTRATION Administration Manual

You must also prepare the cluster nodes for the OES 2 patch process as described in
(Patching) an OES 2 SP2
you update a server from OES 2 SP1 Linux to OES 2 SP2 Linux, the BCC 1.2.1 patch files are
pulled down from the OES 2 SP2 Linux patch channel in the maintenance patch for OES 2 SP2
Linux.
The following BCC 1.2.1 patch is available for OES 2 SP2 Linux:
OES2 SP2 January 2010 Scheduled Maintenance 20100130: The BCC 1.2.1 patch includes
the following RPM files:
novell-business-continuity-cluster-1.2.1.765-0.5.i586.rpm
novell-business-continuity-cluster-idm-1.2.1.758-0.6.noarch.rpm
yast2-novell-bcc-2.13.1.741-0.6.noarch.rpm
The features and changes included in the BCC1.2.1 patch are described in
1.2.1 Patch for OES 2 SP2 Linux (January 2010)," on page
The patch includes a new
resource driver template delivered in the BCC 1.2.1 patch for OES 2 SP2 Linux is functionally
the same as the template delivered in the BCC 1.2.0 patch for OES 2 SP1 Linux, but it has a
different version number. If you are already running Identity Manager 3.6.1 on OES 2 SP1
Linux and have deleted and re-created the Identity Manager drivers to use the new template for
BCC 1.2.0, it is not necessary to delete and re-create the drivers again for BCC 1.2.1.
5.3 Installing the BCC Patch on a Fully Patched
OES 2 SP2 Linux BCC Cluster
Use the procedure in this section to apply the BCC 1.2.1 patch to a fully patched OES 2 SP2 Linux
cluster.
IMPORTANT: In this scenario, it is recommended, but not required, that you migrate the cluster
resources to a different node before installing the BCC patch. The BCC installation process does not
affect the cluster resources that are already in place. It is not necessary to reboot the server in order
for the BCC code changes to be applied.
1 On the Identity Manager node in every peer cluster, save the BCC driver configuration
information, then stop the BCC drivers.
2 If you have not already done so, update the Identity Manager node in each peer cluster to use
Identity Manager 3.6.1, but do not restart or re-create the drivers at this time.
For instructions, see
3.6.1," on page
3 On one peer cluster, use a rolling update approach to install the BCC 1.2.1 patch:
3a (Optional) On one of the nodes in the cluster, migrate its cluster resources to another node
in the cluster.
3b Install the BCC 1.2.1 patch files on the node (where cluster resources are not running).
It is not necessary to reboot the server in order for the BCC code changes to be applied.
58 BCC 1.2.1: Administration Guide for OES 2 SP2 Linux
Server" in the OES 2 SP2: Installation
BCC resource driver template for Identity
Chapter 7, "Upgrading the Identity Manager Nodes to Identity Manager
65.
"Updating
Guide. If BCC 1.2 is installed when
Section 2.2, "BCC
25.
Manager. The BCC