Upgrading BCC
55
no
vd
ocx (
e
n)
1
1
Decemb
er
2
007
7
Click Done to save your changes.
8
Repeat
Step 3
through
Step 7
for the other cluster objects in your BCC.
3.1.6 Verifying SAN Scripts
The BCC 1.1 installation program searches for and updates any SAN scripts that you created for
BCC 1.0. The updates are performed to make the SAN scripts SMI-S compliant. You should check
all SAN scripts after installing BCC 1.1 to ensure that they will perform the desired functions.
3.1.7 Deleting and Re-Creating BCC IDM Drivers
After completing the upgrade procedures in the above sections you must delete the BCC IDM
drivers that were created when you installed and configured BCC 1.0. This includes the cluster
synchronization driver(s), and if you configured User object synchronization, the User object
synchronization driver. You must then re-create those drivers in order for them to work with BCC
1.1. See
Section 2.5.1, “Configuring Business-Continuity-Specific IDM Drivers,” on page 29
.
During a BCC upgrade, BCC 1.0 clusters will be unable to communicate with BCC 1.1 clusters.
This condition exists temporarily until the upgrade has been completed. If an actual disaster were to
occur during the upgrade, a BCC 1.0 cluster can be failed over to a BCC 1.1 cluster.
3.2 Upgrading BCC 1.0 to BCC 1.1 for Linux
To upgrade from BCC 1.0 (NetWare only) to BCC 1.1 for Linux, you must first upgrade all nodes in
BCC 1.0 clusters to BCC 1.1 for NetWare. To do this, follow the instructions in
Section 3.1,
“Upgrading BCC 1.0 to BCC 1.1 for NetWare,” on page 53
.
IMPORTANT:
All cluster nodes in every cluster in your BCC must be upgraded to BCC 1.1 for
NetWare before converting clusters to Novell Cluster Services for Linux.
On one cluster upgrade NetWare cluster nodes to Linux by following the instructions in
Converting
a NetWare Cluster to Linux (http://www.novell.com/documentation/oes/cluster_admin_lx/data/
bu1b1x8.html)
in the
OES Novell Cluster Services 1.8.2 Administration Guide for Linux
.
Clusters containing NetWare and Linux servers are only supported in a BCC as a temporary means
to convert a cluster from NetWare to Linux. Part of the temporary conversion state includes a
restriction that only one mixed cluster can exist in your BCC. For example, Cluster A can have both
NetWare and Linux nodes, but Cluster B cannot. All nodes in Cluster B must be either NetWare or
Linux.
You must re-create the BCC IDM drivers after converting to Linux. See “
Configuring Business-
Continuity-Specific IDM Drivers
” in the
Novell Business Continuity Clustering for Linux
Adminitration Guide
.
Normally, when converting a NetWare cluster to Linux, you need to run the
cluster convert
command after the entire cluster has been converted to Linux. When converting a BCC to Linux, do
not run the
cluster convert
command until all clusters in the BCC have been upgraded and
converted to Linux. See “
Finalizing the Cluster Conversion
” in the
Novell Business Continuity
Clustering for Linux Adminitration Guide
.
