Data migration from clm on premises to CLM on cloud and vice versa
Accepted answer
Hi, Dastan.
If you are using our IBM IoT CE hosted offerings, this is an add-on service performed by our operations team. Due to our responsibility for security, reliability and performance, we do not allow customers that level of access to the system.
If you are using some other hosted service, you would need to discuss this with your hosting service provider.
Comments
Hi Larry,
Dastan,
All configuration customization performed within CLM such as for work items and process work flows are included in the migration export/import process. For migration from our cloud hosted service to another environment (e.g. on premises), our operations team would create a data export and provide access to the exported data for customer retrieval. The service does not include import into another environment. Server side plug-ins and java script are allowed. However, we require a technical review to assess risk to performance, security and reliability. Based on this assessment, we may require the customer to sign a waiver releasing IBM from issues caused by the plug-in(s). Our operations team will deploy the plug-ins to the appropriate location.
Hi Steve,
Thank you for the valuable information. It clears many of my doubts
2 other answers
There are two basic approaches for full data migration from one environment to another. One involves the use of the command line utility "repotools" export/import capability that comes with CLM. The other is to use the database server's export/import capability. The latter, of course, requires the use of the same database server in the cloud environment as it is on-premises. The latter also migrates the full data set, including the data warehouse. The former enables the migration of data between dissimilar database servers. However, the data warehouse is not included and must be rebuilt. In either case, consideration must be given to whether the cloud environment will re-use the system URL as the on-premises environment. If not, a server rename must be performed on the data subsequent to migration. This requires submitting a IBM Support request and carries the risk of introducing performance degradation on the existing data.
Refer to the following article on the migration process...https://jazz.net/library/content/docs/repo-migration/
Comments
Hi Larry,
Here is some information about our standard IBM Collaborative Lifecycle Management on Cloud data import. This import includes Rational DOORS Next Generation, Rational Quality Manager and Rational Team Concert, to the equivalent on Cloud offering. Any database/store that is supported by repo tools, will be supported for the export/import from CLM. Customers are responsible for performing the repo tools export, supported by our CLM operations team, and ensuring bandwidth is available to transfer the files to the Softlayer data center "over the wire". Outages occur during the repo tools export and production import, and until we turn over the CLM on Cloud instance. We expect this to be over a weekend. The data warehouse will be rebuilt using the standard jobs. Customers are responsible for generating a file of users for import.
Reports are not exported/imported by the operations team. JRS reports can be exported and imported by the customer, once the CLM on Cloud instance is up and turned over. Neither Rational Insight, nor any Cognos BI are supported.
Our standard data migration add-on includes one test import to confirm all data is successfully moved, and to determine the amount of time required for the production export/import. Our standard pricing supports an import of CLM 5.0.2 or later, and a maximum of 300 GB database/storage. If you are on an older version of CLM, you have more data, or additional import/exports are required, a SOW will be developed based on the situation.