Migrate SCM Components from RTC 2.0 to RTC 6.0.6
Accepted answer
The summary answer how to migrate RTC SCM data from RTC 2.0 (or 3.x, 4.x, 5.x) to a newer version is:
- The only option to migrate the data with history is to upgrade to that server version. E.g. to RTC 6.0.6 migrate to RTC 3.x then to RTC 4.x, then to RTC 5.x and then to RTC 6.0.6.
- If the history is not required, it is possible to load the data to disc into a sandbox, disconnect that from SCM and manually re-share the data into SCM
-
It would be possible to write automation to do the data export and import. I have written an internal tool that could potentially be useful. However I am not sure if it would even work against RTC 2 (API, Java Version, etc) and if the libraries needed would be available. An attempt would be a service engagement.
-
In some rare occasions distributed SCM could be used to replicate (with history) but that is only possible if the RTC version supports distributed SCM and if the versions are compatible with respect to distributed SCM.
2 other answers
Hi Kiran,
I think you have only option left is to upgrade or as an workaround you have to have a new 606 installation with new code imported and needs to replicate the same stream and code strucutre ( no history will be available)
Regards,
Arun.