recommended roll back plan to be set while upgrading CLM 406 to 501
Dear Team,
Below are the roll back steps I have listed out and let me know if there is any additional steps to be carried out.
Scenario:
We have JTS,CCM,QM and RM installed on four different servers (using Distributed topology)
As a backend we use SQL Server 2008 R2. The Databases will be moved to different SQL Server 2012 instance.
(in our case the 2008R2 database will remain on the 2008 server instance)
___________________________________________
We will be backing up all the conf directory from all the applications and the tomcat config from the JTS Server.
E:\Program Files\IBM\JazzTeamServer406\server\conf (backup of the CLM 406 conf directory)
E:\Program Files\IBM\JazzTeamServer406\server\tomcat\conf (backup of the conf directory from the JTS Server)
In case the new CLM 501 do not work as intended, we can shutdown the new server by going to CLM501 server directory and run the server.shutdown.bat file.
Start the existing CLM406 by copying back the baked up config directories. which I hope will have all the information.
Logically this way it should work. Let us know if there are any extra steps to be carried out.
One answer
How a backup strategy can look like is explained here: https://jazz.net/wiki/bin/view/Deployment/BackupCLM and also how to restore.
You should test your backup and restore works at least in an isolated environment.
You should test your backup and restore works at least in an isolated environment.
Comments
Thanks for providing the URL.
In our case we have these applications running on VM.
From an application standpoint, Is taking a snapshot of the respective VM based on the last working state recommended ?
The main concern here is to consistently backup all the required data (config, index, databases etc). As long as it is unclear where all that data is stored a simple answer is likely more destructive than suggesting to make sure you do backups and test them.
If you have your databases on the same VM's, together with all the app config data and indexes (which is not a very performant architecture), shutting down the image and creating an image might be one option for a backup.