Upgrading
You can upgrade to version 3.1 of TrueSight Vulnerability Management from the following versions:
- 3.0.01, 3.0.01.001
- 3.0
When upgrading TrueSight Vulnerability Management, BMC recommends that you follow the upgrade order outlined in this topic.
Complete the pre-upgrade tasks to ensure a successful upgrade.
| Description | Procedure |
|---|---|
Pre-upgrade activities include backing up various files, creating a local docker registry, and configuring the product for firewall and Security-Enhanced Linux. |
A TrueSight Vulnerability Management deployment upgrade involves upgrading Elasticsearch, application, and SCCM connector (if you are using SCCM as the endpoint manager).
Important: You do not need to upgrade the database as version 3.1 of TrueSight Vulnerability Management supports the same version of PostgreSQL as supported by version 3.0 and 3.0.01.
| Description | Procedure |
|---|---|
Upgrade in the following sequence:
Note: If you are using SCCM as the endpoint manager, you can upgrade it either before upgrading ElasticSearch and application, or after upgrading them. |
What next?
- If you added any trusted certificate before upgrade, you need to add it again after upgrade, as described in Adding a trusted certificate.
- After a successful upgrade, explore the enhanced and new capabilities of the product. See
3.1 enhancements
for more information. - BMC releases periodic product updates through service packs. Check the Release notes and notices section for the latest product updates and apply the ones relevant to your environment.
Comments
Log in or register to comment.