68
Novell Business Continuity Clustering 1.1 for NetWare Administration Guide
no
vd
ocx (
e
n)
1
1
Decemb
er
2
007
Host Server-->Virtual NCP Server
4.21 Blank Error String iManager Error Appears
While Bringing a Resource Online
If you get an error in iManager with a blank error string (no text appears with the error message)
while attempting to bring a resource online, it is possible that Novell Cluster Services views the
resource as secondary even though BCC has changed the resource to primary and iManager shows
the resource as primary.
To resolve this problem, make a change to the cluster properties to cause the NCS:Revision attribute
to increment. You could add a comment to the resource load script to cause this to happen.
4.22 Best Practices
The following practices will help you avoid potential problems with your BCC:
IP address changes should always be made on the Protocols page of the iManager cluster plug-
in, not in load and unload scripts.
This is the only way to change the IP address on the virtual NCP server object in eDirectory.
Ensure that eDirectory and your clusters are stable before implementing BCC.
Engage Novell Consulting.
Engage a consulting group from your SAN vendor.
The cluster node that hosts the IDM driver should have a read/write replica with the following
containers in the replica (filtered replicas were not supported in BCC 1.0):
Driver set container
Cluster container
(Parent) container where the servers reside
Landing zone container
Full read/write replicas of the entire tree at each data center.
4.23 Mapping Drives in Login Scripts
Consider the following when mapping drives in login scripts in a BCC:
Using an FDN (such as map s:=BCCP_Cluster_HOMES.servers.:shared) to a cluster-enabled
volume has been tested and does not work.
When the resource fails over to the secondary cluster, the DN does not resolve to a server/
volume that is online. This causes the
map
command to fail.
Using the
SLP Server Name
/VOL:shared
syntax has been tested and works.
SLP Server Name
is the name being advertised in SLP as specified in the resource load script.
This method requires a client reboot.
See
TID 10057730 (http://support.novell.com/docs/Tids/Solutions/10057730.html)
for
information on modifying the server cache Time To Live (TTL) value on the Novell Client
TM
.
Содержание BUSINESS CONTINUITY CLUSTERING FOR NETWARE 1.1 - ADMINISTRATION
Страница 4: ...novdocx en 11 December 2007...
Страница 10: ...10 Novell Business Continuity Clustering 1 1 for NetWare Administration Guide novdocx en 11 December 2007...
Страница 72: ...72 Novell Business Continuity Clustering 1 1 for NetWare Administration Guide novdocx en 11 December 2007...
Страница 86: ...86 Novell Business Continuity Clustering 1 1 for NetWare Administration Guide novdocx en 11 December 2007...
