It's all about the answers!

Ask a question

RTC V4 Migration Plan

charbak roy (122) | asked Dec 11 '12, 12:42 a.m.
We are having RTC V3.0.1 currently running in our production server.
Now we are planning to upgrade it to RTC V4.
We want RTC V3 should be running and create a separate instance for V4 on the same hardware.
Is there any way to populate V3 DB  data to V4 DB?
We want to test V4 instance before shutting down V3 as it is production environment.

Problem is we don't have any staging/testing environment. So we don't want to touch V3 instance during upgrade. Please suggest immediately.

2 answers

permanent link
Rajat Singh (59833545) | answered Dec 11 '12, 1:08 a.m.
I dont think it is possible to use two jts servers on the same machine.
However, for testing purpose, you may setup another 3.0.1 on a different machine, take the snapshots of your databases and restore them into new database. Then point the testing server to the newly created database. Upgrade this server to v4.0.1.

Also since the data is coming from a different pubclic uri, you may change the same in the client machine host files to point to the test server and not the production.

Hope this helps!!

Best Regards

charbak roy commented Dec 11 '12, 4:53 a.m.

Thanks Rajat.

Can you pls explain by step by step. That will help us to make the upgrade plan.

charbak roy commented Dec 11 '12, 4:56 a.m.

Another question...
If we are doing upgrade on the V3 DB to V4. After migration over, will we have all the Dashbaord, plans, work items as we are currently having in V3 instance or all will be lost? we need to again create all the stuffs manually.

We have taken backup of  the process config file already.

permanent link
Ralph Schoon (63.3k33646) | answered Dec 11 '12, 6:04 a.m.
edited Dec 11 '12, 6:07 a.m.
In general it is suggested to have a test environment to test upgrades. For 4.0.1 this help entry talks about some more details

The Test environment needs to be using the same names used in the public URI and thus needs to be isolated from the production environment. You basically use network techniques such as host entries or unplugging the networs or virtualization to separate them. It is essential that they can not see each other and you can't hook up artifacts of one with the other.

Testing the upgrade is a good way to make sure everything works afterwards and also to answer questions like will the dashboards stay available.

The answer to the latter is, you should see exactly the data you saw before migrating. No data should be lost. While upgrading the data in the database is adjusted to the new schema.

The upgrade process and other details is described in the online help - you should use the interactive upgrade guide to create individual upgrade guides. shows a whole host of other information you can tap into.

Ralph Schoon commented Dec 11 '12, 6:07 a.m.

I forgot to mention that it is not possible and not supported to change the public URI when going to 4.x. So you can't run the old and the new version in parallel in the same network.

4.x introduces a limited capability to rename the servers (after you upgraded to 4.x). See for more information. You need to involve support to get the key required to do that. Support  will determine if the scenario you are trying to do is supported and can't harm your system.

Your answer

Register or to post 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.