copy project across server
One answer
the fact that this is 3.0.1.3 does not help. What I would recommend is the following:
1. upgrade to version 4 (which supports server rename)
2. copy the entire repository to a the new server (make a DB backup and restore on a new DB server)
3. on the new server, perform a server rename so the public uri of CLM matches the name of the new server
4. on the old server, archive the project to be moved
5. on the new server, archive all the other projects
Please note that server rename has it's own limitations (for example regarding integrations).
I believe this entire procedure will keep both of the environments supported.
Comments
if only I could do that. The production infrastructure has projects already in place, and the so the old repository cannot replace it.
not my favourite answer, but there is an enhancement request to allow moving a project across repositories:
https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=87778
Unfortunately, not implemented yet.
What you can do is to export the workitems to CSV and import them to a new server (loosing history, attachments, discussions, etc).
Secondly, you can move the source control using distributed repositories.
Beyond that, I believe you can only recreate data by hand, or write your own custom software to move the data using the Plain Java Client.
thanks.. I knew that was the answer.. its the other stuff.. teams, plans, iterations, ...
Also, note that "server rename" does not help when trying to move a single project area from one server to another. In particular, suppose there are any links between the project area being moved and the project area not being moved. A given repository has exactly one alias at a given time for a given repository URL. So in the non-moved project areas, the alias would continue to point to the original repository, and all references to information in the moved project area would continue to point to the archived copy of that information. And in the moved project areas, the alias would point to the new repository, so any references to the non-moved project areas would be forwarded to the new repository, and not find the artifacts there.
right. Piotr's hopeful suggestion assumed full server conversion in place..