Upgrading The Bcc Cluster From 1.1 Sp1 To 1.1 Sp2 - Novell BUSINESS CONTINUITY CLUSTERING 1.1 SP2 - ADMINISTRATION Administration Manual

You can use the information you documented in
and driver sets. If desired, you can use the same names and port numbers that you used for
BCC 1.0.
5c Repeat
6 Issue the
7 Start the Identity Manager drivers.
8 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
Resource objects for the pool resource, then re-create the cluster resource to get it back to a
usable state in the BCC.
9 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
Cluster Peer Credentials," on page
IMPORTANT: Make sure the administrator username meets the requirements specified in
Section 4.3, "Configuring a BCC Administrator User," on page
10 Verify that Novell Cluster Services and BCC 1.1 SP1 appear to be functioning correctly by
performing the following tests:
10a Create a new BCC enabled pool resource, BCC migrate it between peer clusters, and
verify that it migrates correctly.
10b 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.
10c BCC migrate the pool resource that you modified in
verify that it migrates correctly.
10d Check all SAN scripts ensure that they will perform the desired functions.
11 Continue with
page 60.

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
NetWare 6.5 SP6
BCC 1.1 SP1 for NetWare
Identity Manager 2.x
1 Stop the Identity Manager (formerly DirXML) drivers from running in the Identity Manager
node of every peer cluster in the business continuity cluster.
60 BCC 1.1 SP2: Administration Guide for NetWare 6.5 SP8
Step 5a through Step 5b
command on each server node to have them join the BCC.
ldbcc.ncf
Section 5.3.2, "Upgrading the BCC Cluster from 1.1 SP1 to 1.1 SP2," on
Step 1
for each node in the peer cluster
84.
Step 10b
Final Configuration
NetWare 6.5 SP8
BCC 1.1 SP2 for NetWare
Identity Manager 3.5.1
as a guide for creating the drivers
Cluster
TM
Section 7.2, "Changing
47.
between peer clusters, and