04-04-2014 06:26 AM
I am doing HPSM upgrade from 9.21 to 9.33, please let me know the Process on what all should I keep in mind doing the update, if any of you have done it, can you please share a plan with me.
should I go Module wise or its just a patch upgrade, we have a fully customized change and incident mgmt environment.
Thank you in Advance for helping.
04-04-2014 06:56 AM
it is not just a patch upgrade. Basically you will need to:
1. backup the Database (+ all customizations)
2. install SM 9.30 which is major release
3. install 9.33 which is patch instalation
4. deplyo the old DB
Another option would be to use the upgrade utility
If you find that this or any post resolved your issue, please be sure
to mark it as an accepted solution.
Please also give kudo if you find it interesting :)
04-04-2014 01:13 PM - edited 04-04-2014 04:35 PM
Using the upgrade utility is not "another option"; you must use it to upgrade your system. You can update the RTE and web tier to 9.33 but if you then just connect to the production database, you will stil be running 9.21 applications (the applications are part of your database data and the only way to update them is by using the Application Upgrade and Application Patch utilities).
You need to:
--update the server software/ RTE
--update the clients
--use the upgrade and patch utilities to bring your SM applications up to the new version.
--generate a patch which can then be used to update production.
--TEST the patch repeatedly against a production copy until it is validated. This is the single most important part of the process. Repeat testing until you are intimately familiar with the process to apply the patch and have verified the resulting system is correctly upgraded.
--use that to upgrade prod.
The attached HP document outlines the specific steps for an upgrade from 9.20 to 9.33 (Because 9.21 is a minor release, this is the appropriate guide--there is not a separate guide for 9.21).
Problems we've encountered with customers (don't do these :-)
- Skipping the entire application upgrade piece (e.g. upgrading only the server RTE and clients).
- Applying the application upgrade, but not completing the reconciliation process to resolve conflicts between tailored objects and any objects modified in the new application version. This can have, um, hilarious results.
- Not testing the patch against a production copy until right before they've scheduled the upgrade of production, leaving no opportunity to correct any issues.