H.3.3 Installing Business Continuity Clustering
Location
"Identity Manager Engine
and eDirectory Driver" on
page 43
H.3.4 Managing a Business Continuity Cluster
Location
Chapter 10, "Managing a
Business Continuity Cluster,"
on page 91
Section 10.1.1,
"Understanding BCC
Resource Migration," on
page 91
H.3.5 Removing Business Continuity Clustering Core Software
This section is new.
H.3.6 Troubleshooting Business Continuity Clustering
Location
Section 10.16 Slow Failover
H.3.7 Upgrading Identity Manager Nodes to Identity Manager
3.6.1
Location
Section 6.1, "Upgrading to
32-Bit Identity Manager
3.6.1," on page 61
Section 6.2, "Upgrading to
64-Bit Identity Manager
3.6.1," on page 61
Change
Each Identity Manager node must be online in its peer cluster and Identity
Manager must be running properly whenever you attempt to modify the
BCC configuration or manage the BCC-enabled cluster resources.
Change
IMPORTANT: Identity Manager must be configured and running on one
node in each peer cluster before any BCC enabled cluster resource
changes are made. Make sure that the Identity Manager server is part of
the cluster and that it is working properly whenever you make BCC
configuration changes to the BCC-enabled cluster resources. For
information, see
Chapter 8, "Configuring the Identity Manager Drivers for
BCC," on page
67.
The scan for devices follows the unload script and load script runs.
Change
This section was removed. It applied only to BCC 1.1 for NetWare.
Change
It is not necessary to re-create the BCC drivers if you perform an in-place
upgrade of 32-bit Identity Manager 3.6 to 32-bit Identity Manager 3.6.1.
Upgrading to 64-bit Identity Manager 3.6.1 requires a rebuild of the 64-bit
cluster node and a re-creation of the BCC drivers.
Documentation Updates 175
Need help?
Do you have a question about the BUSINESS CONTINUITY CLUSTERING 1.2 - ADMINISTRATION and is the answer not in the manual?
Questions and answers