Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

how to migrate/export RTC 3.0.1.2 from Server A to Server B(A&B have different hostname, different OS)?

Hi,

I am trying to migrate my RTC 3.0.1.2 setup and its Database DB2 from Solaris machine to another RHEL 6.4 machine having DB2 and RTC 3.0.1.2.My plans is to migrate/configure RTC 3.0.1.2 on this new host and then update it to RTC 4.0.6. I have few question for that, would be great if someone could guide me of the recommended way for doing this.

1). Can the 2 hostnames be different, I mean is it feasible to migrate or configure RTC having the same JTS and Jazz data on new host having different Hostname?
2). Can DB name be different on the 2 servers?
3). Is using RTC export and import utility correct way of migrating data.If not what is the correct way.
4). Can i restore my DB2 from solaris box to RHEL box.


Following is the error that i am getting while registerting my applicaiton :-

An error occured while attempting  to access the Application About service listed in the Discovery document for this application. Please ensure that the application has been installed  and provisioned correctly. ID CRJAZ2080E

Unable to register my application via /jts/setup
I have used :-repotools-jts.sh resetRepoLockId and repotools-jazz.sh resetRepoLockId

Thanks in advance.


0 votes



2 answers

Permanent link
Hi Dhruv,
Answers on your questions:

1). Can the 2 hostnames be different, I mean is it feasible to migrate or configure RTC having the same JTS and Jazz data on new host having different Hostname?

A1. For CLM 3.x hostname must be the same. Since CLM 4.0 you can use server rename feature if you want to use RTC on a different host.


2). Can DB name be different on the 2 servers?
A2. Yes. You must use repotools -export and -import commands to migrate them. Alternatively you can use another tools provided from your db vendor

3). Is using RTC export and import utility correct way of migrating data.If not what is the correct way.
A3. See answer on 2

Also you can look at this link: https://jazz.net/wiki/bin/view/Deployment/BackupCLM to see which data to move across repositories.

Let us know if that helps.

1 vote


Permanent link
Dhruv,

1). Can the 2 hostnames be different, I mean is it feasible to migrate or configure RTC having the same JTS and Jazz data on new host having different Hostname?
No. See: https://jazz.net/library/article/749

There is a way to change the public URI - called server rename. See https://jazz.net/library/#sort=pubDate&tag=server%20rename for articles around this.Server rename is only supported for certain cases. In your case I would suggest to move the host name to the new server to avoid it. You should also, as mentioned in the documentation and the setup, always choose a public URI (host name) that is independent from the machine. This allows to move the CLM servers to newer hardware without being dependent on the actual name of the machine.

2). Can DB name be different on the 2 servers?
You configure the DB name in the connection properties (teamserver.properties) as long as the data is there, you can choose any name you want. Please refer to your DB documentation if you can use a backup/restore across the different architectures. You should have the DB on a DB layer that is independent from the application server host. In this case.

3). Is using RTC export and import utility correct way of migrating data.If not what is the correct way.
You can use the repotools to migrate the database as described in the documentation (migration section), however, that is not enough. See below.
 
4). Can i restore my DB2 from solaris box to RHEL box.
Yes. Using repotools.


To migrate to another server, you have to basically
  • Install the server on the new machine
  • Move the files mentioned in https://jazz.net/wiki/bin/view/Deployment/BackupCLM to the new server. Configuration, indexes, custom extensions, plugins. 
  • Change the DB connection to your new DB's you created
  • Change the hostname of the old server and switch it over to the new server
  • Deploy CLM (WAS), configure LDAP
  • Run the repotools import
  • Launch the server - a new Setup is NOT required. You don't register.

See

https://jazz.net/forum/questions/101883/physically-move-rtc-on-tomcat-from-one-server-to-another-server

https://jazz.net/forum/questions/64301/how-to-move-jazzserver-to-new-hardware

There where a lot of discussions around this scenario in the forum. I would try to search for more discussions here. I couldn't find the ones I was looking for, except the ones above so far.


1 vote

Your answer

Register or log in 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.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details
× 2,356
× 119
× 84
× 3

Question asked: Jul 31 '14, 1:19 a.m.

Question was seen: 6,748 times

Last updated: Jul 31 '14, 3:05 a.m.

Confirmation Cancel Confirm