Rollback / Downgrade from CLM 4.01 to 3.0.1.4
We need to plan a roll-back strategy (i.e.: roll-back to 3.0.1.4 in case of a failed change, for whatever reason).
Does anyone have a procedure/pointers/experience with a version roll-back?
WebSphere server (on one server), Oracle database (on another).
Thanks
Ron
3 answers
Consider reading this article to understand what are the important things to backup. I believe restoring the databases, index files, your application server profile configuration and application configuration (the .../server/conf folder) are essentially needed to be restored. If you have additional components in your topology then they probably needs to be considered as well.
Hope this helps
Comments
One of the keys to that article in this case would be Backing up and restoring the Jazz Team Server.
Comments
Thanks Sean, we'll be keeping our 3.0.1.4 around for a safe period.
Because of the changes in the db schemas, and with intent to be able to salvage any new record edits in the 4.0.1 environment made before roll-back, it doesn't look like we could just bring over the db used in the 4.0.1 back over to the 3.x environment.
So, alternatively, I am wondering about a strategy such as daily xml exports in the 4.0.1 environment (during the period we agree to ensure roll-back capability) a possible work-around allowing us to go back to 3.x, then re-import the xml files into the old db (so we don't loose the new work).
Assuming that we have all of that backed up that you mentioned, Indradri, can we restore those to a 3.0.1.4 instance? As I understand it, the database schema has changed in CLM 4.0.1, so would it be possible to restore a database?
Comments
You would need to take a database backup (ask your DBA to take it on the DB side) first before you run the repotools command.
Hi Chris,
During the upgrade process you need to run the upgrade scripts which makes some changes in the application databases but incase there is a need to rollback, if you restore your databases from a backup which was taken before starting the upgrade process, your databases should be back to what is was prior to the upgrade.
One thing to note: Installing another version of CLM ought to go into another location so the basics of the previous version should remain intact. i.e. updated files would go into the new 4.0.X install. Most important is the database backup.
This makes sense, if we wanted to revert to the same state of the data when we were in 3.0.1.4.
But, what if we wanted to keep the data/source code, work items, etc...for the month that they used 4.0.1, but then realized we wanted to 3.0.1.4 back but wanted to keep the work we've done.
Is there any way to avoid data loss for the month that the users were active during 4.0.1?
Hrm... don't think there is any script to help you downgrade the database schema from 4.0.1 to 3.0.1.4. You might want to raise a PMR to IBM Support to have this answer.
Chris, I am curious to know what problems would you anticipate for which you need to rollback to a earlier version after a planned and successful upgrade.
But to answer your question and as per my understanding some data may not fit back to the earlier release even if you plan to export it back, after rolling back to the earlier version.
Hope this helps