Performing the upgrade

Configuration changes required before upgrading

IT Data Analytics does not support installation using root user. It is mandatory to have a non-root user access to be able to install on a Linux computer. As a non-root user, ensure that you have the write permissions to the directory in which you want to install the product.

• To perform the installation on a remote Linux computer, enable the X Window System and set the DISPLAY variable to launch the installer user interface. To do so, run the following command:
  DISPLAY=hostName:0.0
export DISPLAY
  where hostName refers to the name of the computer on which you want to launch the installer.

• Before installing or upgrading on Linux, you must modify certain system configuration settings. You must do so by logging on as a root user and change the required configurations by either one of the following ways:

  • By running a script preinstallconfig.sh located in the Utility folder
    To configure the minimum values by executing a script, the minimum requirement for installing the indexer component is to run the following utility with root user.
    

    Though the Truesight IT Data Analytics installation or upgrade in Linux needs to be carried out as a non-root user, the utility needs to be run with root user.

    <INSTALLER_LOCATION>/BMC-TrueSight-IT-Data-Analytics/Disk1/utility/preinstallconfig.sh
    Examples:
    

    sh preinstallconfig.sh MODIFY_CONFIG <NON_ROOT_ITDA_USER>

    sh preinstallconfig.sh ALL <NON_ROOT_ITDA_USER> <ITDA_INSTALL_DIR>
    

    In the above examples, <NON_ROOT_ITDA_USER> is the non-root username with which you want to install Truesight IT Data Analytics. After you run the script, log on again by opening a new Linux user session before launching the installer. This utility ensures that the minimum required system configurations are carried out for Truesight IT Data Analytics installation. The following table shows the possible arguments that this command can take:
    

    Possible script arguments	What the script does
    /bin/bash preinstallconfig.sh ALL <NON_ROOT_ITDA_USER> <ITDA_INSTALL_DIR>	-Modifies the owner of TrueSight IT Data Analytics with the given new TrueSight IT Data Analytics owner. -Updates the system configuration files if required. -Allows write permission to the system directories and files for the new TrueSight IT Data Analytics owner. NOTE:-If TrueSight IT Data Analytics is not installed in the Linux environment, the parameter <ITDA_INSTALL_DIR> would be used for creating the directories and a new owner is set for this location.
    /bin/bash preinstallconfig.sh MODIFY_OWNER <NON_ROOT_ITDA_USER> <ITDA_INSTALL_DIR>	-Modifies the owner of TrueSight IT Data Analytics with the given new TrueSight IT Data Analytics owner. NOTE: If TrueSight IT Data Analytics is not installed in the Linux environment, the parameter <ITDA_INSTALL_DIR> would be used for creating the directories and a new owner would be set for this location.
    /bin/bash preinstallconfig.sh MODIFY_CONFIG <NON_ROOT_ITDA_USER>	-Updates the system configuration files if required. -Allows write permission to the system Directories and files for the new TrueSight IT Data Analytics owner. NOTE: If TrueSight IT Data Analytics is already installed with a non-root user, then executing the script MODIFY_CONFIG will be sufficient.

    If the script finds the environment variable BMC_ITDA_HOME either from environments or from /etc/bmc.profile, then the script assumes that the current installation would be an upgrade path. The script will modify the owner of the directory set to BMC_ITDA_HOME.

  • By manually configuring the properties in the configuration files 
    Before manually configuring the properties, you need to give write permissions to the following directories:
    

    Directory	Needed to...
    /opt	Needed by the installer to create the ProductRegistry.xml file. The ProductRegistry.xml file maintains registry of the BMC product installations on the host. Note that you need to create the opt/bmc directory. Recommendation BMC recommends you to not modify the location and the content of this file to avoid any upgrade issues.
    /opt/bmc

    To change the system configurations manually, add the properties as given in the following table to the limits.conf file or the sysctl.conf file as specified.
    

    You must configure the values given in the table using values with root user permissions.

    Filename	Property	Description
    /etc/security/limits.conf	<NON_ROOT_ITDA_USER> soft nofile 65536 <NON_ROOT_ITDA_USER> hard nofile 65536	The number of open files must be at least 65536.
    	<NON_ROOT_ITDA_USER> soft nproc 4096 <NON_ROOT_ITDA_USER> hard nproc 4096	The number of open processes must be at least 4096.
    	<NON_ROOT_ITDA_USER> soft memlock unlimited <NON_ROOT_ITDA_USER> hard memlock unlimited	The memory lock should be set to unlimited.
    	<NON_ROOT_ITDA_USER> soft as unlimited <NON_ROOT_ITDA_USER> hard as unlimited	The maximum Virtual memory should be unlimited. To configure the value for non-root user, some operating systems require that root user should also have unlimited maximum virtual memory. In such instances, add the following lines: root soft as unlimited root hard as unlimited
    /etc/sysctl.conf	vm.max_map_count=262144	Maximum Map Count  is the maximum number of memory map areas a process may have.The virtual memory property max_map_count must be configured to at least 262144.

    After configuring the virtual memory, execute the following command to refresh with the new configuration::

    sysctl -p

  After making the configuration changes either by running the script or manually, log on again by opening a new Linux user session and launch the installer.

Applying the Fix Pack before upgrading

If you are using IT Data Analytics 2.7.00 in your environment and planning to upgrade to 11.0.00 or later, you must apply the IT Data Analytics 2.7.00.001 Fix Pack before you proceed to upgrade. For more information, see  2.7.00.001: Fix Pack 1  and follow the instructions to apply the fix pack.

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.

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.

1. Configuration Database

2. Indexer

3. Upgrade the following components (order is not important):
   
   • Collection Station
   • Console Server
   • Search

Upgrading the product or particular product components

1. 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.

   
   

2. Read the license agreement and agree to the terms. Click Next.

3. 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.    

4. Click Install to start the upgrade.  

5. (Optional) Click View Log to see the installation log.

6. 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

7. 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.

    

8. (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.

9. (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 .

Post-upgrade notes

When you upgrade from previous versions of IT Data Analytics to IT Data Analytics version 11.0.00, data from the previous version, is migrated to the newer version. Depending on the data size, the migration may take some time. Search features of IT Data Analytics like histogram, facets and search counts of older data will be available only once the migration is complete.

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 11.0.00 of the product:

• Horizontal scaling recommendations
• Vertical scaling recommendations

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.

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 11.0 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 Remedy Single Sign-On as your authentication mechanism by running the enablesso CLI command CLI command. Using Remedy 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.