r2 - 2015-05-27 - 16:55:34 - Main.sbagotYou are here: TWiki > 
Deployment Web > DeploymentTroubleshooting > UpgradeTroubleshooting > CLMUpgradeTroubleshooting > BackupBeforeUpgrade
Deployment Web > DeploymentTroubleshooting > UpgradeTroubleshooting > CLMUpgradeTroubleshooting > BackupBeforeUpgrade ![]()
What to backup prior to an upgrade
Authors: StephanieBagot, UpgradeTroubleshootingTeamBuild basis: CLM 3.x and later
This page will discuss the necessary configuration and file backups required prior to beginning an upgrade with the Collaborative Lifecycle Management (CLM) family of products (Rational Team Concert, Rational Requirements Composer, and Rational Quality Manager).
Error During Upgrade:
Backing up indices failed.
Resolution: Check the repotools-jts_backupJFSindexes.log file for details as to why the backup failed.
What to backup
Below is a list of the necessary items to backup prior to an upgrade:- WebSphere Application Server profile
- Application Database, Data Warehouse Database
- Local Indices through repotools-jts -backupJFSIndexes
Errors which may occur
Below discusses some errors which may occur at this stage of the upgrade processrepotools-jts -backupJFSIndexes
Version: Upgrade to 4.xError During Upgrade:
Backing up indices failed.
Resolution: Check the repotools-jts_backupJFSindexes.log file for details as to why the backup failed.
Related topics: None
External links:
- None
Additional contributors: StephanieBagot,
-
Deployment web
-
Planning and design
- Installing and upgrading
- Migrating and evolving
- Integrating
- Administering
- Monitoring
- Troubleshooting
Community information and contribution guidelines 
Topic list 
Search 
Advanced search 
Notify 
RSS 
Atom 
Changes 
Statistics 
Web preferences 
NOTE: Please use the Sandbox web for testing -
To do
-
Under construction
-
New
-
Updated
-
Constant change
- None - stable page
- Smaller versions of status icons for inline text:
-
Copyright © by IBM and non-IBM contributing authors. All material on this collaboration platform is the property of the contributing authors. Contributions are governed by our Terms of Use. Please read the following disclaimer.
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.