Preparing for upgrade
This section describes the precautions you must take, the tasks you must perform when preparing to upgrade your system, and the procedure to download the upgrade files.
Before you begin
Before you upgrade, make sure that:
- You backup your database because the BMC Discovery upgrade process performs an upgrade of the database. You can restore an 11.3.x backup to a 20.02 (12.0) appliance.
- The location used by the upgrade for temporary files must be readable by the
tidewayuser. The default location (which is created if it does not exist) is
/usr/tideway/tmp, and can be changed using the command line option
- To upload the upgrade archive using the UI, you must have sufficient space in
/tmp, approximately 1.6 GB.
- You are a user with admin security privileges, such as the system user.
Upgrade archive naming conventions
The upgrade archive files are available from the BMC Electronic Product Distribution (EPD) site. To help you locate the files easily, the Product Name column lists the label name of the product. For example, BMC Discovery. Click the + sign next to it to expand and view the available downloads. Locate your required product version, operating system, and version, such as BMC Discovery 12.0 CentOS 7. When you click this product label name, the relevant upgrade archive file is ready for download. Select Save File and then click OK.
The product upgrade archive file uses a
.tgz file extension, while the compressed OS upgrade archive uses the
.sh.gz file extension. The downloadable file uses the following file naming convention:
- For product upgrades:
Vnis the BMC Discovery version number to which you are upgrading to and
nnnnnnis the build number.
For OS upgrades:
Where v is the version number, and
yy.mm.ddis the date of the last package update from CentOS or Red Hat, and
nnnnnnis the build number.
To download the upgrade files
- From the BMC Electronic Product Distribution (EPD) site, download the compressed upgrade archive.
You must follow specific file naming conventions for the compressed archive files. For more information, seeupgrade archive naming conventions.
Upload the upgrade archive to the
/usr/tideway/var/upgradedirectory on the standalone machine or any machine in the cluster.
If you are using a browser that supports HTML5, you can upload the archive using the upgrade UI.
To upload the upgrade archive using the UI, you must have sufficient space in
/tmp, approximately 1.6GB.
When you run the upgrade, the timezone you specified is overwritten and reset to Europe/London unless you have updated the timezone. For information about how to configure the timezone, see Localizing the appliance.
- You can re-run the upgrade if it is terminated or fails. Destructive actions are recorded and are skipped on subsequent upgrade runs. Consequently when an upgrade is re-run, it is usually significantly quicker. You are unlikely to need to run the upgrade more than once, as it would only be required if an upgrade fails. See also the
tw_run_upgradecommand to re-run an upgrade.
- Where an upgrade makes changes to syncmapping files (see Default CDM Mapping and Syncmapping block), the initial CMDB syncs after upgrade might result in longer reconciliation times. Examples of such changes are key changes or attribute changes on a CMDB CI.
Where SQL and JDBC credentials are in use, their existing properties files continue to be used and updated properties files are installed but not used. Where such credentials are unused, the old properties files are replaced with the latest.
The upgrade converts any existing Integration Points to database data sources. The name of converted Integration points is ip_name.connection_name, where ip_name is the name of the Integration Point, and connection_name is the name of the connection used for the Integration Point. After the upgrade you should ensure that your converted Integration Points are available on the Data Sources page.
The upgrade enables HTTPS whether or not it was previously enabled, and existing certificates are used. Self-signed certificates are created if the 11.3.x appliance was not using HTTPS, these can be replaced by a certificate from a publicly trusted certificate signing authority if required.
Approach to upgrading consolidating systems
If you are upgrading a scanning appliance you may have to also upgrade the consolidation appliance. Version 11.0, 11.1, 11.2, 11.3, and 20.02 (12.0) scanning appliances can consolidate to version 20.02 (12.0) consolidating appliances. However, version 20.02 (12.0) scanners cannot consolidate to earlier consolidating appliances. Once you have upgraded your consolidating appliances, you can then upgrade scanning appliances as required. You must upgrade all your appliances eventually.
Patches were released for 11.x appliances which cause a potential loss of data between unpatched scanning appliances and patched consolidating appliances. BMC Discovery 20.02 (12.0) incorporates those changes. This means that the earliest patch versions you can safely use as a scanner when consolidating to BMC Discovery 20.02 (12.0) are:
- 11.0 patch 6
- 11.1 patch 8
- 11.2 patch 6
- 11.3 patch 5
When a system uses consolidation, we recommend the following approach in upgrading BMC Discovery:
- Stop discovery on scanning appliances.
- Ensure that all consolidation operations are complete.
- Stop discovery on consolidating appliances.
- Upgrade consolidating appliances.
- Restart discovery on the consolidating appliances.
- Restart discovery on the scanning appliances.
- Upgrade scanning appliances as required.