How to migrate RTC server and repo to different servers?
We have an RTC instance on one server (RTC 1.0 and DB2 database) that have been runing for some time (meaning some production data exist). Now we need to migrate the instance to a new RTC web/application server and a new DB2 server. Could you please comment on the migration procedure? Let's take work items as examples, will the work items have new IDs in the new RTC instancxe and new DB2 database? Please keep in mind that we will migrate to different servers and there is no network communication between the current server and the new servers.
|
8 answers
|
Does the following procedure sound right? Thanks.
1. Backup the DB2 database on the old server db2 backup database {db-name} user <userName> using <password> to <target> COMPRESS 2. Run repotools to copy the contents of the Jazz repository on the old server to a TAR file. repotools -copy toFile=temp.tar source.teamserver.properties=./source.teamserver.properties target.teamserver.properties=./target.teamserver.properties 3. Copy the TAR file onto the new server. 4. Instrall RTC1.0 on the new server. 5. Create a new DB2 database on the new server. Do NOT create RTC tables again. A blank DB2 database should be used. 6. Run repotools to import from the TAR file. repotools -import fromFile=./export_filename.tar 7. Edit the teamserver.properties file on the new server to reference the new database. 8. Perform other RTC configuration on the new RTC server. |
If the db2 versions match, you can do a db2 backup of the original db and do a db2 restore on to the new db. This way u don't need to go through migration and you will have the db ready within 2 hrs.
Please note that you need to copy the lucene text index directory from original server to the new server. ---- Balaji Jazz Server Team |
The repotools -copy command is effectively an -export and an -import, so
to use it you must have BOTH the source database and the target database installed and available. Your teamserver.properties files for both databases must also be configured correctly. When using the repotool -copy command you do NOT need to use the -import command, since this should already have happened. The TAR created by the -copy command can be deleted once you have confirmed that the copy worked successfully. We do not delete it, since you might need to use it to do an import (using the -import command) if the -copy command failed for some reason unrelated to Jazz. Simon Archer Jazz Server Team |
|
Thank you, Balaji and Simon. I will try restoring the database first.
Balaji, could you please specify which directory is the "the licene text index directory"? Thanks. |
|
Go to https://{YourServerName}:9443/jazz/admin , click on Advanced Properties link on the left.
Search for FullText. Find the property value for "Index Location" property. For e.g. if the index location property value is "/opt/IBM/Jazz/", then there would be directory "/opt/IBM/Jazz/fulltext_index2" directory on the server. Copy that directory from source to destination machine and set the index location appropriately in the target machine. ---- Balaji Jazz Server Team |
|
In Full Index section, I only saw one value Index location ---- workitemindex. This is a Windows server.
Thanks. |
This makes the index location relative to the working directory of the server (which makes it work out-of-the-box, independent from the installation folder). By default you would find the "workitemindex" folder in the same folder your server.startup.bat is. The index location is also logged during server startup, try searching your log for "Fulltext Index Location".
Regards, Christof Jazz Work Item team yanli wrote: In Full Index section, I only saw one value Index location ---- |
|
This is the line in the log file. Searched for "fulltext_index" in Windows Explorer, there is no such file or directory. Any comment? Thanks.
09:41:20,150 INFO m.team.fulltext.service.internal.index.IndexConfig - Fulltext Index Location: workitemindex\fulltext_index\ |
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.