Performing the upgrade

This topic provides information about upgrading the TrueSight IT Data Analytics product from an earlier version.

The upgrade process requires you to upgrade all the components of the product to the latest version. For example, you cannot use Collection Station of an earlier version with all other components upgraded to the latest version. This is important to avoid potential problems and errors.

Notes

Upgrading to IT Data Analytics 2.7.00 requires version 2.5.00 or version 2.1.00 to be already installed. Skipping releases is not supported for versions prior to 2.1.00.
Collection Agents are not considered to be one of the product components. For more information about the product components, see the product architecture.

This topic contains the following information:

Before you begin

Ensure that the following requirements are met:

Read the 2-7-00-enhancements to understand the features and improvements available with this release.
See the Post-upgrade notesto see the changes applicable with this release, then follow the upgrade instructions to perform the upgrade.
Ensure that all the components of the product are up and running.
Depending on your operating system, ensure that the following environment variable is already set.The [confluence_table-plus] macro is a standalone macro and it cannot be used inline. Click on this message for details.
This macro generates standalone content. As a consequence you need to make sure to use a syntax that separates your macro from the content before and after it so that it's on a line by itself. For example in XWiki Syntax 2.0+ this means having 2 newline characters (a.k.a line breaks) separating your macro from the content before and after it.
Create a back up of all the indexed data at an appropriate location. For more information, see Backing-up-and-restoring-data.

Upgrade sequence in a multiple-server deployment

If you are operating in a multiple-server deployment, the order in which you upgrade the components and the order in which you start the components is important.

Note

Unless upgrade of all the components is completed, do not start any of the component services.

You need to upgrade the components in the following order of priority. The following order also applies for starting the services post-upgrade. For more information, see Starting-or-stopping-product-services.

Configuration Database
Indexer
Upgrade the following components (order is not important):
- Collection Station
- Console Server
- Search

Upgrading the product or particular product components

Start the installation program by running the setup (for Windows) or setup.bin (for Linux) file. Click Next.
Note
In a multiple-server deployment, if you have multiple instances of a product component, then you need to run the upgrade individually on each of the computers hosting that product component. The upgrade sequence is important while upgrading in a multiple-server deployment.
Read the license agreement and agree to the terms. Click Next.

The type of installation you performed (earlier), determines the type of upgrade. Depending on the type of upgrade, perform the steps described in the following table:

Upgrade type	Steps
Typical install	Depending on your platform, you can choose to keep the following check box selections unchanged and click Next: (Windows only) Check box for pinning the product to your Start menu, and starting the product services immediately after the upgrade is complete. (Windows and Linux) Check box for starting the product services immediately after the upgrade is complete.
Custom install	The product components to be upgraded are automatically displayed as per your earlier installation. Click Next. (Windows only) The check box for pinning the product to your Start menu is displayed. You can choose to keep the default selection unchanged and then click Next.

The Installation Preview screen is displayed, providing information about the features to be installed, the total disk size, the destination directory, and so on.

Click Install to start the upgrade.
(Optional) Click View Log to see the installation log.
To exit the installation program, click Done.
By default, the following environment variable pointing to the product installation path is automatically set:

Windows
Linux
%BMC_ITDA_HOME%
$BMC_ITDA_HOME
To view the upgraded version of the product, reload the current browser page so that the cached content is ignored.
Tip
Reload the page by pressing Ctrl+F5 on the browser page.
(Optional) To apply enhanced security checks and to prevent CSRF attacks, you might want to configure the system before you can access it. For more information, see Configuring-access-URLs.
(Optional) If you want to enable security for the Console Server, you need to configure the system. For more information, see Enabling-security-for-the-Console-Server-and-Search-components .

Windows	Linux
%BMC_ITDA_HOME%	$BMC_ITDA_HOME

Post-upgrade notes

After you upgrade, search on field values works in a case-insensitive way on new data collected. Conversely, search on field values that form part of existing data (or old data) continues to work in a case-sensitive way.

Case-insensitivity for field and tag values can impact existing saved searches and associated dashboards and notifications. As a result of case-insensitivity, it is possible that you see more results on running the saved search as compared to the previous version of the product. Also, case-insensitivity can impact the product performance if you are operating in a large scale environment. For more information, contact BMC Support. Additionally, you can see the following topics that provide scaling recommendations for version 2.7.00 of the product:

You can turn case-insensitive searches into case-sensitive searches by adding the CASE function in the search string. For more information, see Search-string-syntax.

Note

After upgrading, if you create an Upload file type of data collector to collect past data, then it is possible that the data collected is added to an existing index. As a result, search performed on this data will work in a case-sensitive way.

If you have existing external configurations for TrueSight Infrastructure Management (or ProactiveNet) cells, then you might need to edit them and change the encryption key. Changing the encryption key is required if TLS is enabled for TrueSight Infrastructure Management on TrueSight Operations Management 10.7. In this scenario, you also need to import the certificates generated on the TrueSight Operations Management side to be able to create new external configurations in version 2.7 of IT Data Analytics. For more information, see Enabling-security-for-communication-with-Infrastructure-Management-server.

Troubleshooting a failed upgrade

While running the upgrade, it is possible that you see the Feature Configuration Database failed error on the Installation Summary screen. This error is likely to occur in a scenario if you upgraded from version 2.0.00 to 2.1.00 and then to 2.7.00. This issue can occur due to a conflict between a user and its role mapping that might have occurred in version 2.1.00 of the product. To resolve the issue, please contact BMC Support.

If you face any other upgrade-related issues, consider rolling back to an earlier version before you try upgrading again. For more information, Rolling-back-a-failed-upgrade.

Where to go from here

(Optional) Start using Atrium Single Sign-On 9.0 as your authentication mechanism by running the enablesso-CLI-command CLI command. Using Atrium Single Sign-On is important if you plan to use IT Data Analytics in conjunction with the TrueSight products. For more information, see User-authentication-options.