IBM Support

Support Policy for High Availability clustering and ClearCase

Question & Answer


Question

What is the support policy for IBM Rational ClearCase configured in a High Availability clustered server configuration on UNIX or Linux operating systems?

Answer

As of ClearCase version 7.1, support for the following was added:




As of ClearCase version 7.0.1, the following solutions are supported for High Availability with Rational ClearCase.





Refer to the Rational ClearCase System Requirements List for further details regarding supported version requirements.

Review the ClearCase Administrator's Guide on the topic of Configuring Rational ClearCase for high availability for more information.

There are a variety of change requests (RFEs) to add support of this functionality with ClearCase on different operating systems:

  • RATLC01012276 - Microsoft Cluster Server
    Refer to record ID 88 on the IBM Rational Software RFE Community for updated information or to provide feedback.

  • RATLC00585651 - Sun Cluster
    This RFE has been closed as there are no plans to address the request in the near future, but may consider it at a later time.
  • RATLC00587506 - HP Service Guard
    This RFE has been closed as the decision was made by Product Management to exclude the resolution of this feature enhancement from future upgrades and releases of ClearCase.


Refer to technote 1131230 Support Policy for Windows Server Datacenter Edition and ClearCase for information about Windows Datacenter Edition support.



Information about ClearCase Remote Client (CCRC)



A ClearCase VOB server can be aliased and if this host has a problem, then a new host can be configured using the same alias name. This cuts down the time a view or VOB needs to be restored, reregistered, tagged and allows the new host to be ClearCase functional in a short amount of time.

However, with CCRC the physical hostname is used by the CCRC clients so aliasing the hostname or clustering is not currently supported in CCRC. The CCRC view references are tied to the hostname and not the alias name of the host so restoring the views to an aliased hostname is not an option.

[{"Product":{"code":"SSSH27","label":"Rational ClearCase"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Operating System Configurations","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"}],"Version":"7.0.1;7.1;7.1.1;7.1.2;8.0;8.0.1;9.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
16 June 2018

UID

swg21127354