RQM data center migration and server rename
Hi all,
I need to migrate RQM from one data center to another, it means from one server to another with a different DNS name. At the same time, I will upgrade RQM from 3.0.1.3 to the latest 5.0.1.
Environment: RedHat Linux 6.4 and Oracle 11g
As first approach, I was about to backup/restore the oracle BBDD. Is it possible to perform the server rename process afterwards? If so, is it supported this scenario?
Due to the customer constraints, I cannot first upgrade from 3.0.1.3 to 5.0.1 and afterwards migrate from one server to another.
Does anyone have any experience in this type of migration? If so, what is the best suitable procedure to follow?
Is it possible to use the repotools export/import to perform this task? maybe RQM Copy Utility?
Thanks very much in advance!
Accepted answer
Hi Ismael,
The Last June I was involved in a similar proyect.
I followed these steps:
1. Migration of the CLM server 3.0.1
You can use Repotools only when the DB migration is from one vendor to other vendor, For example from
Derby to Oracle.
If the source and target DB are Oracle you need to use the Oracle tools for the migration of the DB
2. Upgrade from CLM 3.0.1 to 4.0.7 in the new Server
3. Upgrade from CLM 4.0.7 to 5.0.1
4. Rebuild the CLM indices
5. Server Rename of the CLM 5.0.1
Before the server rename you need that the new server resolved the old and new hostname
The old server should be stopped before start the DB migration and you could not start the service until the step 5 will be finished.
My experince was that the more critical task is the DB migration, since for large installation the data migration could take long time and you need a DB admin with good knowledge about this subject.
I hope that this information would be useful and you can free contact with me to get more info...
Regards
Javi
The Last June I was involved in a similar proyect.
I followed these steps:
1. Migration of the CLM server 3.0.1
You can use Repotools only when the DB migration is from one vendor to other vendor, For example from
Derby to Oracle.
If the source and target DB are Oracle you need to use the Oracle tools for the migration of the DB
2. Upgrade from CLM 3.0.1 to 4.0.7 in the new Server
3. Upgrade from CLM 4.0.7 to 5.0.1
4. Rebuild the CLM indices
5. Server Rename of the CLM 5.0.1
Before the server rename you need that the new server resolved the old and new hostname
The old server should be stopped before start the DB migration and you could not start the service until the step 5 will be finished.
My experince was that the more critical task is the DB migration, since for large installation the data migration could take long time and you need a DB admin with good knowledge about this subject.
I hope that this information would be useful and you can free contact with me to get more info...
Regards
Javi
4 other answers
I think if you look at the documentation you can not perform a server rename on 3.x you must be at least 4.x before you can do a server rename. Repotools will not help you on this either.
There are some tricks with DNS you could play to get the server moved and then upgrade and then do the server rename but they are not supported. I would suggest contacting support and see if they can suggest a mechanism.
The Copy Utility was never meant to be used as a 'Project Copy', but rather as a means to re-use specific test assets. It is however capable of performing a Deep Copy; this is not a full copy Project Area, but the majority of the Project Area assets are copied
I would fully review the Known Limitations sections of the Wiki (https://jazz.net/wiki/bin/view/Main/RQMCopyUtility#Known_Limitations) so that you have a full understanding on what and what does not get copied
Note: If you are copying across servers, you need to be at the exact same version in order to use the tool
Ismael,
As Dave mentioned, Server Rename support was introduced in version 4.0; so you would need to be at the minimum version of 4.0 to proceed.
If you were to move the data (as is) you need to be able to access it using the same Public URI as used from its original location. Then , once upgraded, you can perform a server rename
There may be some other options such as putting a Reverse Proxy in place in the new location so that the original Public URI can still be used
Comments
Hi,
I'm afraid that I cannot upgrade the original location to version 4.X, and perform the server rename afterwards.
I was actually thinking about the reverse proxy in case the DNS name was different, but unfortunately the same WAS server is used by other tools (ClearCase and ClearQuest), so they would also be affected. Anyway, I will suggest again this reverse proxy approach to the customer.
What's your opinion about the RQM Copy Utility? I remind you that there are more than two years of RQM information, and the migration has to be done in maximum a couple of days.