Configuring DevOps Code ClearCase for high availability

All cluster nodes must run the same version and patch level of the platform operating system, Veritas Cluster Server, and DevOps Code ClearCase or DevOps Code ClearCase MultiSite software. DevOps Code ClearCase views, VOBs, registry database files and DevOps Code ClearCase MultiSite data must use shared network storage (dual-ported, multi-initiated, or SAN-attached). DevOps Code ClearCase MultiSite shipping configuration on all cluster nodes must be identical; scheduled jobs in MultiSite environments must have identical parameters on all machines in the cluster. Failover of view servers with views exported for non-ClearCase access are not supported in high-availability environments.

DevOps Code ClearCase high availability is supported for asymmetric (active/standby) configurations, where DevOps Code ClearCase is active on only one cluster node at a time. The failover node must have DevOps Code ClearCase installed, but not running. VCS failover service groups enforce this behavior. In the event of a failover or switchover, VCS stops DevOps Code ClearCase on the master node and starts DevOps Code ClearCase on the failover node. Failover is 1x1 (server to server).

Restoration of normal service (to the original cluster configuration) after a failover requires manual intervention by an administrator. DevOps Code ClearCase clients who access servers protected by a VCS cluster must use the virtual host names provided by VCS for those servers. From the DevOps Code ClearCase client’s point of view, a failover/switchover will look the same as a temporary network interruption. Some client commands might recover before the RPC timeout expires; if they do not, an RPC timeout error or connection failure is reported, and the client must try the command again.