Upgrading from BCC 1.0 to BCC 1.1 SP2 while leaving the BCC configuration in place is a two-phased process where you must perform an intermediate upgrade to BCC 1.1 SP1 on NetWare 6.5 SP6 as follows:
You must perform the upgrade sequence on every node in each peer cluster that is part of your existing business continuity cluster.
IMPORTANT:Before you begin, review Section 4.1, Requirements for BCC 1.1 SP2 for NetWare.
During a BCC upgrade, Business Continuity Clustering 1.0 clusters are unable to communicate with Business Continuity Clustering 1.1 clusters. This condition exists temporarily until the upgrade has been completed. If an actual disaster were to occur during the upgrade, a Business Continuity Clustering 1.0 cluster can be failed over to a Business Continuity Clustering 1.1 cluster.
Perform a rolling cluster upgrade for each peer cluster from BCC 1.0 to BCC 1.1 SP1 to achieve the intermediate configuration as follows:
|
Initial Configuration |
Intermediate Configuration |
|---|---|
|
NetWare 6.5 SP5 BCC 1.0 Identity Manager 2.x iManager 2.5 or 2.6 |
NetWare 6.5 SP6 BCC 1.1 SP1 for NetWare Identity Manager 2.x iManager 2.6 |
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 in Step 5.b when you re-create the drivers.
Stop the Identity Manager (formerly DirXML) drivers from running on the Identity Manager node of every peer cluster in the business continuity cluster.
Perform a rolling cluster upgrade for all nodes in a peer cluster:
Issue the cluster leave command on one node in the cluster.
Update NetWare 6.5 from version SP5 to SP6, and apply the latest patches for NetWare and Novell Cluster Services.
You can perform a script upgrade by using NWCONFIG.
For information, see the NW65 SP8: Installation Guide.
See the Business Continuity Clustering 1.1 Readme file for instructions on mandatory patches.
Issue the cluster join command on the node.
Upgrade Business Continuity Clustering from version 1.0 to 1.1 SP1 by installing BCC 1.1 SP1.
IMPORTANT:Do not start BCC at this time.
The Business Continuity Clustering 1.1 installation program automatically detects if Business Continuity Clustering 1.0 is installed and performs the necessary updates to convert 1.0 to 1.1. This includes searching eDirectory for SAN scripts and updating those scripts to be SMI-S compliant.
For installation instructions for BCC 1.1 SP1, see Running the Business Continuity Cluster Installation Program
in the Novell Business Continuity Clustering 1.1 for NetWare Administration Guide.
If the node is running iManager, update the following iManager plug-ins by uninstalling the existing NPM files, and then re-installing the correct iManager NPMs.
Repeat Step 3.a through Step 3.e for each node in the cluster.
Repeat the rolling cluster upgrade in Step 3 for each peer cluster.
On the Identity Manager node in each peer cluster, delete and re-create the Identity Manager driver sets for the cluster:
Delete the Identify manager 2.x driver sets.
Create new Identity Manager driver sets and the BCC drivers with the new BCC 1.1 SP1 templates.
IMPORTANT: Do not create a new partition when creating the driver set.
You can use the information you documented in Step 1 as a guide for creating the drivers and driver sets. If desired, you can use the same names and port numbers that you used for BCC 1.0.
Repeat Step 5.a through Step 5.b for each node in the peer cluster
Issue the ldbcc.ncf command on each server node to have them join the BCC.
Start the Identity Manager drivers.
BCC disable and enable each BCC resource to make sure the BCC attributes are updated.
If a BCC enabled resource is missing BCC attributes, try deleting the eDirectory™ Cluster Resource objects for the pool resource, then re-create the cluster resource to get it back to a usable state in the BCC.
Reset the cluster peer credentials between clusters.
The BCC Administrator user credentials that were set for BCC 1.0 do not work with BCC 1.1. A fully distinguished eDirectory name (FDN) was required for BCC 1.0, but BCC 1.1 requires only the BCC administrator name.
For instructions on resetting BCC Administrator user credentials, see Section 7.2, Changing Cluster Peer Credentials.
IMPORTANT:Make sure the administrator username meets the requirements specified in Section 4.3, Configuring a BCC Administrator User.
Verify that Novell Cluster Services and BCC 1.1 SP1 appear to be functioning correctly by performing the following tests:
Create a new BCC enabled pool resource, BCC migrate it between peer clusters, and verify that it migrates correctly.
Make a load script change (for example, add a space character and save the change) to an existing BCC resource that was created with 1.0, allow the revised load script to synchronize, then verify that the load script was updated at all eDirectory locations.
BCC migrate the pool resource that you modified in Step 10.b between peer clusters, and verify that it migrates correctly.
Check all SAN scripts ensure that they will perform the desired functions.
Continue with Section 5.3.2, Upgrading the BCC Cluster from 1.1 SP1 to 1.1 SP2.
In the second phase of the upgrade from BCC 1.0, you perform a rolling cluster upgrade for each peer cluster from BCC 1.1 SP1 to BCC 1.1 SP2 to achieve the final configuration as follows:
|
Intermediate Configuration |
Final Configuration |
|---|---|
|
NetWare 6.5 SP6 BCC 1.1 SP1 for NetWare Identity Manager 2.x |
NetWare 6.5 SP8 BCC 1.1 SP2 for NetWare Identity Manager 3.5.1 |
Stop the Identity Manager (formerly DirXML) drivers from running in the Identity Manager node of every peer cluster in the business continuity cluster.
Delete the Identity Manager 2.x drivers and driver sets on the Identity Manager node of every peer cluster.
Perform a rolling cluster upgrade from NetWare 6.5 SP6 to SP8 for all nodes in a peer cluster:
Issue the cluster leave command on one node in the cluster.
Upgrade NetWare 6.5 from version SP6 to SP8, and apply the latest patches for NetWare and Novell Cluster Services.
You can perform a script upgrade by using NWCONFIG.
For information, see the NW65 SP8: Installation Guide.
If the node is running iManager, update the storage related plug-ins for iManager.
After upgrading to NetWare 6.5 SP8, iManager no longer displays the roles for Clusters, Storage, and DirXML. The storage related plug-ins require special handling because some storage features were reorganized in the NetWare 6.5 SP8 release. For information, see Storage Related Plug-Ins Must Be Uninstalled
in the NW65 SP8: Readme.
NOTE:The DirXML plug-ins will be replaced by Identity Manager 3.5.1 plug-ins in Step 5.
In iManager, uninstall the old iManager plug-ins for Novell Cluster Services (ncsmgmt.npm), NSS (nssmgmt.npm), Archive and Version Services (arkmgmt.npm), and Storage Management, (storagemgmt.npm).
In iManager, install the new set of storage-related plug-ins for iManager 2.7.2 from the NetWare 6.5 SP8 installation media:
Stop Tomcat 5 by issuing tc5stop command.
Reset Apache 2 by using the ap2webrs command.
Start Tomcat 5 by using the tomcat command.
Wait at least 5 minutes for the iManager changes to take effect, then restart iManager.
In iManager, verify that BCC tasks are available in the role.
Repeat Step 3.a through Step 3.c.g for each node in the cluster.
On each node in the cluster, upgrade Business Continuity Clustering from version 1.1 SP1 to 1.1 SP2 by installing BCC 1.1 SP2.
IMPORTANT:Do not start BCC at this time.
For instructions, see Section 4.0, Installing Business Continuity Clustering.
On the Identity Manager node in the cluster, upgrade Identity Manager from version 2.x to 3.51.
For information, see Upgrading
in the Identity Manager 3.5.1 Installation Guide.
Before you begin, make sure that the Identity Manager node meets the 3.5.1 upgrade requirements.
Upgrade Identity Manager from version 2.x to 3.51.
IMPORTANT:Do not start the drivers yet.
The upgrade updates the Identity Manager software and its plug-ins for iManager 2.7.2 on the same node.
Stop Tomcat 5 by issuing tc5stop command.
Reset Apache 2 by using the ap2webrs command.
Start Tomcat 5 by using the tomcat command.
Wait at least 5 minutes for the iManager changes to take effect, then restart iManager.
In iManager, verify that is available.
IMPORTANT:In iManager, the Identity Manager plug-ins are displayed as version 3.6. The 3.6 version functions properly with Identity Manager 3.5.1.
Issue the cluster join command on each node in the cluster.
Issue the ldbcc.ncf command on each node to have them join the BCC.
Verify that Novell Cluster Services and Business Continuity Clustering appear to be functioning correctly by migrating a BCC enabled resource between peer clusters.
Create the new BCC driver sets for Identity Manager.
On the Identity Manager node in every peer cluster, create the new Identity Manager drivers with the new BCC 1.1 SP2 templates.
IMPORTANT:Do not create a new partition when creating the driver set.
As a guide, you can use the information from Step 1 and Step 5.b in Section 5.3.1, Upgrading the BCC Cluster from 1.0 to 1.1 SP1.
Start the new Identity Manager drivers for each peer cluster.
Verify that Novell Cluster Services and BCC 1.1 SP2 appear to be functioning correctly by performing the following tests:
Create a new BCC enabled pool resource, BCC migrate it between peer clusters, and verify that it migrates correctly.
Make a load script change (for example, add a space character and save the change) to an existing BCC resource that was created with 1.0, allow the revised load script to synchronize, then verify that the load script was updated at all eDirectory locations.
BCC migrate the pool resource that you modified in Step 13.b between peer clusters, and verify that it migrates correctly and that the Identity Manager drivers are synchronizing.
Check all SAN scripts ensure that they will perform the desired functions.