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

Existing test environment with production database

Hi all,´

I have a production platform with IBM CLM 4.0.7 and we plan to migrate to 5.0.2. Of course I would like to try it on another platform before. I already have a test platform (version 4.0.7) but the databases are almost empty and the best I think would be to have some "real" databases to simulate the migration in a environment close to the production one.

There´s a new platform (version 4.0.7) that has never been used (without any databases attached) and I would like to use it to connect some old backups from the production and to get some real datas for the migration.

My question is to know if I can run the custom setup and connect these databases ?

0 votes



One answer

Permanent link
You can basically restore a backup on such a machine. You have to make sure that the production server and the test server machines are isolated against each other, because you have to run the test system with the same public URI the production server has. For Backup see: https://jazz.net/wiki/bin/view/Deployment/BackupCLM You can ask support for a server rename key in order to rename the test environments public URI: http://www-01.ibm.com/support/knowledgecenter/SSCP65_5.0.2/com.ibm.jazz.install.doc/topics/c_redeploy_server.html?lang=en

Please note, that also in the case of a rename, you must avoid linking elements across the production and the test server.

0 votes

Comments

Hi Ralph, thanks for the fast answer. Of course I know this solution but my problem is that I can´t have this 2 platform isolated from each other. Any ideas how I can do that ?

You basically can't as far as I know. The only other solution is to
1. Create a backup of your whole system
2. Take the prod offline
3. Test with your prod system
4. Restore prod from the backup

I can not suggest this solution.

@rschoon,

Will this not work:
1.    Remove the QA environment from the network.
2.    Change the public URI of the QA server to match the production server.
3.    Restore the production db backup to the QA Db server and change the configuration to the new Tables. Dont reinstall the QA Server.
4.    Run the server rename script provided by IBM Support
5.    Bring the QA Environment back to the network
6.    Re-Index

If the customer is hosting the applications in virtual machines, will this be easier:
1) Restore the clone of all VM Hosting all CLM Servers & Production Db Server in an isolated environment.
2) Run the Server rename script provided by IBM Support team.
3) Bring QA environment to the network.

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
× 7,499
× 6,126
× 82
× 8

Question asked: Feb 16 '15, 9:08 a.m.

Question was seen: 4,159 times

Last updated: Oct 02 '15, 11:01 a.m.

Confirmation Cancel Confirm