Why upgrading matters
Upgrading ClearCase to stay on the latest version matters as older versions eventually go out of support, leaving you without security patches, bug fixes or technical support. Many industries (finance, healthcare, aerospace and defense) also require use of supported software for audits and certifications. The latest versions also include security enhancements where known security gaps are addressed that could expose repositories and developer assets. They also include stronger integrations and improved authentication/authorizations, with SSL/TLS support aligning with enterprise security standards.
Newer versions often reduce latency, improve reliability and scale better. Fixes to known defects and bottlenecks are included, leading to more predictable performance.
Older ClearCase versions may not run on newer Linux/Windows servers, storage, or virtualization platforms.
New versions work better with Jenkins, ClearQuest, DevOps Plan, Microsoft Visual Studio, RAD, RSA Designer, Review Board, Virtuoso Studio and VS Code. They also include improved GUI’s and Web Interfaces which allow easier adoption for new users. There are also enhancements to UCM and MultiSite which allow for better replication, activity management, and distributed development support. Staying current with ClearCase reduces the total cost of ownership by reducing firefighting with unsupported tools and helps avoid costly extended support contracts and emergency consulting.
In summary:
Upgrading ClearCase is not just about having the "latest version." It’s about security, compliance, performance, compatibility, and long-term risk reduction. Organizations that delay upgrades face higher risks of system failures, unsupported infrastructure, and costly migrations under pressure.
Upgrade or migration
When to upgrade over migrating to a new environment?
|
Criteria
|
Upgrade
|
Migration
|
|
Definition
|
Upgrade is performed directly on the existing ClearCase servers and infrastructure
|
Migration is performed on a new set of ClearCase servers and infrastructure
|
|
Downtime
|
Requires longer downtime as existing servers that are being used are upgraded
|
Less downtime as the installation, testing and validation is done on a new environment
|
|
Risk Level
|
High – if the upgrade fails rollback can be complex and time consuming
|
Low – the current system remains while the migration, testing, and validation are done
|
|
Roll Back
|
Difficult – requires full backup to restore
|
Easy – the old environment remains until the new environment is running
|
|
Testing
|
Limited – due to the impact on users and production
|
Extensive – the new environment can be tested and validated with an exact copy of the current environment prior to the migration
|
|
Hardware OS
|
Must be compatible; Existing hardware/OS may have limitations
|
Flexibility to use the latest hardware/OS that supports the new ClearCase version
|
|
Configuration
|
Retains the existing configuration and integrations which may include legacy issues
|
Clean setup with opportunity to reconfigure, optimize, and remove legacy issues.
|
|
Cost
|
Low – requires no new infrastructure
|
Higher – requires new servers and possibly storage and/or network resources.
|
|
Time To Implement
|
Fast – if everything goes smoothly
|
Slower – as a new environment must be built and tested
|
|
Impact On Users
|
High – they are impacted from the start of the upgrade until finished or a rollback is done
|
Low – users continue to work in the old environment until they are migrated to the new one after testing and validation; This can also be done in stages
|
|
Scalability & Future Growth
|
Limited by current infrastructure and design
|
Allows re-design for scalability, HA/DR, and future growth
|
|
Best Use Case
|
Small environments with limited resources – where downtime is acceptable and rollback risk is manageable
|
Large, business critical environments needing high availability, minimal downtime, and safe rollback options
|
Upgrade prerequisites and compatibility considerations
Upgrade Prerequisite
- Take a full backup of VOBs, Views (not recommended), Registry, and ClearQuest (if integrated). It’s always good to take a full server image backup to recover fast from disaster. Verify recovery procedures before starting.
- Ensure valid ClearCase licenses. Confirm vendor support for the target version.
- Check minimum CPU, memory, and disk space availability.
- Check supported OS versions and patch levels.
- Check compatibility for versions of Oracle/DB2 (if used for ClearQuest or other integrations).
- Verify WebSphere/Tomcat compatibility where applicable.
- Notify users of downtime. Freeze code check-ins during the upgrade window.
- Create a staging/test environment set up for a dry-run upgrade.
- Validate tools/scripts against the new version.
Compatibility Considerations
Ta
- Ensure the target ClearCase version supports Windows/Linux/Unix flavors and versions in use.
- Check version alignment across MultiSite replicas.
- Check UCM project/stream compatibility during mixed-version scenarios.
- Verify IDE plugins and versions (Eclipse, Visual Studio, RAD, RSA etc)
- Check CI-CD tools (i.e., Jenkins) and ClearQuest integration compatibility.
- Check the supported mixed client/server version matrix.
- Check the minimum client version required post-upgrade: https://www.ibm.com/support/pages/node/477019
- Validate custom triggers, type managers, and scripts.
- Verify VOB schema and Feature level compatibility, and ClearQuest schema migration dependencies.
- Define rollback procedures if the upgrade fails and validate snapshot backups for fallback.
ClearCase Pre-upgrade assessment and environment preparation
ClearCase Pre-upgrade assessment:
Current Environment Inventory
- Document ClearCase version, test fixes applied, and fix packs in use.
- List all ClearCase servers: Master server (Multisite) and other replica sites, VOB servers, Registry servers, License servers, View servers, and CCRC WAN servers.
- Capture OS version, kernel version hardware specifications, storage configurations.
- Identify integrations in use (ClearQuest, Jenkins, Rational Team Concert, custom scripts, etc.).
- Note any 3rd-party dependencies (antivirus, backup tools, LDAP, NFS, etc.).
Licensing & Support Readiness
- Verify license server version compatibility with the target ClearCase version.
- Check the availability of sufficient ClearCase licenses.
- Confirm support timelines for current and target versions.
VOB & View Health Checks
- Run checkvob for corruption or inconsistencies.
- Verify dbcheck results for VOB databases.
- Identify and clean up orphaned views, temporary views, or unused VOBs.
- Validate backup and recovery procedures for VOBs and views.
Performance & Capacity Review
- Check current storage utilization of VOBs and views.
- Confirm available disk space for upgrade operations and rollback snapshots.
- Validate network performance between sites (especially for MultiSite/CCRC).
Integration & Customization Audit
- Assess compatibility of ClearQuest, ClearTeam Explorer, and other Rational tools.
- Document triggers, type managers, scripts, and customizations.
- Verify if APIs or automation need adjustments after upgrade.
Environment Preparation Before Upgrade:
Backup & Recovery Plan
- Take full backups of VOBs, Views (Optional), Registry, ClearCase configuration files.
- Test restoration procedures to ensure rollback capability.
Test & Validation Environment
- Set up a sandbox/test environment mirroring production.
- Perform a trial upgrade with representative VOBs and views.
- Validate ClearCase functionality, triggers, and integrations in the test setup.
Compatibility & Upgrade Path Validation
Stakeholder Readiness
- Communicate planned downtime/maintenance windows.
- Align with development teams for code freeze during upgrade.
- Provide user readiness/training for UI or workflow changes.
Security & Access Controls
- Review and update ClearCase users, admin privileges and admin group membership.
- Validate LDAP/AD integration settings for authentication.
- Ensure consistent group mapping across domain/sites.
Monitoring & Post-Upgrade Support Plan
- Enable monitoring/logging for ClearCase services.
- Define post-upgrade validation checklist (deliver, rebase, build, MultiSite sync, etc.).
- Assign support owners for rapid rollback in case of issues.
Backup Strategy
- Full VOB & View (Optional) Backup – ensure all VOB storage directories, views, and global/admin VOBs are backed up.
- ClearCase Registry & Config Backup – preserve registry database, license data, host/user configs.
- System-Level Backup/Snapshot – take OS or VM snapshots of ClearCase servers before upgrade.
- Database Integrity Check – run checkvob/dbcheck before backup to ensure clean state.
- Backup Validation – confirm backups are restorable (test a restore of a sample VOB).
Recovery Strategy
- Keep pre-upgrade server snapshots/configs ready for quick rollback.
- Confirm the ability to restore VOBs, Views, and registry files from backups.
- Pre-define steps for restoring the environment in case of upgrade failure.
- Practice restoring on a non-production/test system to validate the process.
- Have an optional standby server with the pre-upgrade setup for fast failback.
Validation and testing steps
Core Service Verification
- Check if ClearCase services are running without errors.
- If the environment is a CCRC WAN server along with ClearCase services, WAS and IHS services should be checked.
- Verify ClearCase license server is functional.
- Confirm ClearCase registry is accessible from all servers and clients.
VOB & View Validation
- Run cleartool lsvob and ensure all VOBs are listed and accessible.
- Mount VOBs using ‘cleartool mount <vob-tag>’ and check access.
- Validate global VOBs and admin VOBs are operational.
- Run ‘cleartool lsview’ and ensure all views are visible.
- Start and test both dynamic views and snapshot views.
Data Integrity Checks
- Run ‘cleartool checkvob/dbcheck’ on critical VOBs to verify database consistency.
- Validate symbolic links and derived objects (DOs) if used.
- Check if any VOB requires schema and feature level upgrades.
- Validate that all multisite replicas are synchronized.
Client Connectivity
- Test ClearCase client connectivity from different platforms (Windows, Linux, UNIX if applicable).
- Verify developers can check-out/check-in files.
- Test deliver/rebase operations in UCM projects.
Functional Tests
- Test cleartool commands (lsactivity, mkbranch, mklabel, diffbl, etc.).
- Verify trigger scripts and config specs are working as expected.
- Validate multisite replication (if used) – run multitool lsepoch, and test synchronization.
Performance & Stability
- Compare VOB access time before vs. after the upgrade.
- Test build operations with dynamic views.
- Monitor logs (albd, view_log, vob_log) for errors/warnings.
Backup & Recovery Confirmation
- Take a post-upgrade backup to capture the new stable state.
- Test restoring at least one VOB from backup in a test area
Upgrade Assistance
Submit a proactive support case to request assistance with upgrade planning and technical assistance during the upgrade. Our support teams are glad to work with customers who are in the process of planning a ClearCase upgrade. During the migration / upgrade phase, discussions will be held to:
- Understand environmental details and challenges if any
- Provide relevant documentation to assist with upgrade preparation
- Guide the key contacts who will be performing the upgrade
Note: The advantages of being on the latest supported version, are:
i. Customers can get 24*7 support, based on the severity / priority of the issue
ii. Customers can get test fix (hot fix) versions on top of a fix pack, as applicable