How to clone a CLM installation?
We have RTC/RRC 4.0.6 on Windows via Tomcat7 service, in a TEST env, which is a pre-PRD env, where we verify evey modification or addition prior to implementation in PRD; and a PRD env.
We are trying to build a third env, a real sandbox for POC and we happen to get it in time to test our next upgrade, to 5.0.2,
My strategy is to take advantage of existing PRD data to populate the new sand box hence:
Once 4.0.6 is running:
Have never installed from scratch or cloned an installation to a pristine env, I wonder if this is a sound plan. Would appreciate any input or advice.
Would it be better and faster to clone than to install 4.0.6 from scratch then run setup to use same URIs and point to new DB server ?
If having issues with cloning, would running setup at that point help ?
|
Accepted answer
The root cause of the issue was my stupidity of forgetting to shut down the apps (duh!) while zipping the install area.
Ralph Schoon selected this answer as the correct answer
Comments Also, you should only copy the files that need copying e.g. reinstall the products and then deploy the backup over them.
long TRUONG
commented Feb 23 '15, 6:38 a.m.
Thx Ralph,
Learning the hard way, not only on copying but also on expecting cloned DBs on a silver platter (like before) complete with access, same account, sane passwd; also on trying to replace encrypted passwd with new raw passwd in the properties files instead of getting RTC up lame, but with DB connection to input/encrypt new passwd : Got there more than 2 weeks behind schedule
|
2 other answers
Ralph Schoon (63.3k●3●36●46)
| answered Feb 06 '15, 4:50 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
|
I would suggest you automate the env creation/deployment/upgrade process in scripts and use tools like vagrant to create a new env. Most of the tasks are scriptable (from experience as I have done it myself).
Liora
|
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.
Comments
First obstacle: Tomcat files too long (believe to be the name not the path) to be compressed; e.g.
Am doing a direct server to server copy, these files (over 2000 of them) cannot be copied either, and they have to be skipped. Wonder if that is because they are NTFS junction points which cause infinite loops.
<o:p> </o:p>