The following practices help you avoid potential problems with your BCC:
IP address changes should always be made on the Protocols page of the iManager cluster snap-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 Identity Manager driver should have a read/write replica with the following containers in the replica (filtered replicas were not supported in Business Continuity Clustering 1.0):
Driver set container
Cluster container
(Parent) container where the servers reside
Landing zone container
Ensure that you have full read/write replicas of the entire tree at each data center.