Individual Project Migration to new server
We have an operational RTC server in Seoul, and just installed a new RTC server in Atlanta, both are v2.0.0.1. Our goal is to migrate a single project from Seoul to Atlanta. In addition, Seoul would prefer to not stop the server.
The procedure for migrating an entire DB is documented in the Jazz Library (http://jazz.net/library/LearnItem.jsp?href=content/docs/repo-migration/index.html) To my knowledge, there is no command switch for repotools to export only a single project (http://jazz.net/forums/viewtopic.php?t=2337&highlight=project+migration&sid=bd7099e46fc2a33ed3161704687796a2) Questions: 1. What is the best solution for single project migration? 2. Can the export be done without stopping the server? |
3 answers
We are working on this feature for RTC 3.0.
https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/93151 The plan is move the project when the source and target repositories are online. --- Balaji Jazz Server Team We have an operational RTC server in Seoul, and just installed a new RTC server in Atlanta, both are v2.0.0.1. Our goal is to migrate a single project from Seoul to Atlanta. In addition, Seoul would prefer to not stop the server. |
Thanks for the reply. This is good news for R3.0. However, since I can't wait, can you please confirm that you are implying the following:
1. The best solution for R2.0 is to migrate DB and archive projects on the target server that are not of interest. 2. The server must be stopped to export the DB with repotools. If you had a different alternative in mind, I'd like to know as this is not ideal. Allan |
Hi Allan,
The solution you described is your only option. --- Balaji Thanks for the reply. This is good news for R3.0. However, since I can't wait, can you please confirm that you are implying the following: |
Your answer
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.