How To
Summary
This document offers some guidance as to what to consider before an upgrade.
Steps
When, planning an upgrade consider the following points:
- You must upgrade one major release at a time. This means to get to v39 from v36.1 you must run two installers, v36.1 -> v37.x -> v38.x-> v39.x.
- You are advised to install the latest point release, indicated by ".x"
- With the recently adopted VRMF numbering scheme, you still need to upgrade sequentially, updating the "Modification" value as follows
- 50.x -> 51.0.0.x -> 51.0.1.x -> 51.0.2.x -> 51.0.3.x
- The third number, or the "Modification" number, is determined to be a "major release" which replaces the previous numbering convention of 47.x -> 48.x -> 49.x
- You are advised to install the latest point release, indicated by ".x"
- Read IBM Documentation thoroughly.
- Pay careful attention to What's New sections.
- Be aware of the upgrade procedure.
- Download the required files from IBM Fix Central.
- Ensure you have all the files required for your environment.
- Ensure you have a tested backup and restore process.
- Ensure you have the relevant resources available.
- Test the upgrade on a non-production server.
- This is especially important if you have integrations connecting to IBM QRadar SOAR.
- Do you have enough disk space available?
- Is DR enabled?
- Plan to upgrade IBM Resilient Circuits and or AppHost?
- Be aware whether you are using an IBM QRadar SOAR provided OVA or IBM QRadar SOAR is installed on your own instance of RHEL.
- If you use your own instance of RHEL do not install the security update file, use yum instead.
- Create a change request and make other teams within your organization aware of the upgrade.
- Check that you know whom to call should you come across a problem.
- Details of how to contact IBM QRadar SOAR support is documented in Support details for IBM QRadar SOAR Incident Response Platform including how to call someone should you have a severity 1 production outage.
- Be aware of the working hours of IBM QRadar SOAR support for non-severity 1 cases.
This list is not a definitive list of points that need careful consideration. All environments are different and each deployment needs a bespoke set of considerations before an upgrade is initiated.
Should you need assistance with formulating a methodology get in touch IBM Security Expert Labs by email, by contacting you Customer Success Manager or your sales representative?
Additional Information
- If you are at all unsure of the upgrade procedure, see IBM QRadar SOAR: Software update cases and support policies for details as to how the IBM QRadar SOAR support team can assist you before the upgrade.
- If you need further information on how to perform the upgrade, our learning academy has short videos you can review describing the process:
- If a case is opened before the upgrade, IBM QRadar SOAR support does not keep this case open.
The IBM QRadar SOAR support team is dispersed across numerous time zones. It is better to open a new case at the time of the problem so that the case is routed immediately to the team that is working to ensure your case receives prompt attention.
Include the update_database_x.log, where the x represents the timestamp of the database upgrade should you open a case with support.
Related Information
Document Location
Worldwide
[{"Line of Business":{"code":"LOB24","label":"Security Software"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSIP9Q","label":"IBM Security SOAR"},"ARM Category":[{"code":"a8m0z000000cwJlAAI","label":"Installation \/ Upgrade"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Version(s)"}]
Was this topic helpful?
Document Information
Modified date:
26 June 2024
UID
ibm16347566