In OES 23.4 with BCC installed and configured, enabling only the TLS v1.3 protocol in the sfcb.cfg file makes the BCC cluster connections to break. To avoid this and maintain stable connections, enable TLS v1.2 as well.
When a BCC-enabled pool cluster resource is brought online in a peer cluster other than where it was originally created, you cannot add a new volume on the pool. The volume is created on the disk, but the Volume object fails to be added to Novell eDirectory with Error 613: Error adding volume to NDS.
We recommend that you create only one volume per pool cluster resource. If you need to add a volume on a BCC-enabled pool cluster resource, you must BCC-migrate the resource back to the peer cluster where the pool was originally created.
In some disaster situations, it is possible that the pool cluster resource has been permanently relocated to the current peer cluster. To cluster-enable the pool in its current cluster, see Permanently Relocating a Cluster Resource to a Peer Cluster in the OES 23.4: BCC Administration Guide.
In the BCC 2.6 release, multiple-tree configurations of business continuity clusters are not supported. All peer clusters must reside in the same tree.