Preparing to upgrade Infrastructure Management

Before upgrading the TrueSight Infrastructure Management server, ensure that your environment meets the upgrade requirements, and complete the tasks described in this section:

General prerequisites

Prerequisites common to Windows and Linux

• Ensure the following Health Check Tool tasks are completed:

  1. Download, install, and run the latest version of the TrueSight Health Check Tool.
  2. From the TrueSight Health Check Tool report saved at the following location, search for the Upgrade Impact  issues:
     
     • (Windows)%BPPM_SERVER_HOME%\utility\TrueSightHealthCheck\reports 
     • (Linux)$BPPM_SERVER_HOME$/utility/TrueSightHealthCheck/reports location. 

  3. Resolve all the issues.

  4. Run the TrueSight Health Check Tool again and ensure that there are no issues found in the report.

  Note: The installer will not allow you to continue the upgrade process if there are issues found in the Health Check Tool report.
• Determine whether you can upgrade directly to the current version or if you must perform a phased upgrade from the earlier versions. For more information, see Supported upgrade paths for TrueSight Operations Management.
• Contact BMC upgrade experts through the AMIGO program , and upgrade only after they confirm that the environment is ready for an upgrade.
• Review the Troubleshooting version 11.3.04 upgrade and post-upgrade issues to ensure that you are aware of workarounds before starting the upgrade.
• Ensure that you have installed the nslookup on both Windows and Linux.
• As a best practice and to avoid a file lock happening during the upgrade process, exclude the installation directory from the on-access virus scanner. For more information, see On-access virus scanners.
• Ensure that you have upgraded the TrueSight Presentation Server to version 11.3.04. For details about version compatibility matrix, see Presentation Server, Infrastructure Management, and PATROL Agent compatibility matrices.
• Review the System requirements and product compatibility for Infrastructure Management  for TrueSight Infrastructure Management.
• Apply the latest fix pack or feature pack on the current version of the Infrastructure Management server to ensure that the server has specific fixes that may not be available in the the version that you plan to upgrade.

• Close all the open files and folders in the current session. Also, close other user sessions on the server before upgrading.

• Take a backup of the Infrastructure Management server, database, and configurations. If the servers are on virtual machines, remember to copy snapshots of the TrueSight Infrastructure Management server(s) and Integration Service hosts. For information, see:
  • Archiving or backing up the Infrastructure Management Server

  • Backing up configuration and database files (SAP SQL Anywhere)

    Additional 7 GB disk space

    Ensure that the host machine has an additional 7 GB disk space to store a backup of the existing TrueSight Infrastructure Management server, which is automatically created during the upgrade process and to copy the installation files for the new version of the TrueSight Infrastructure Management server as shown here:
    To copy the installation zip or tar file copied to the target server you need at least 3.3 GB and to unzip or untar these files you need at least 3.4GB.  Therefore, an additional 6.7GB (3.3 GB + 3.4 GB) capacity is needed for just copying the zip files and and unzipping them. 

• Take a backup of the BPPMServerInstalledConfiguration.xml file present in the <Infrastructure Management server Installation directory> directory. This file contains all the configurations including the user-defined configurations. If the upgrade fails, you can revert to the existing configurations using this configuration file.
• Stop access to the TrueSight Infrastructure Management database from other BMC products such as TrueSight Operations Management Reporting, or TrueSight Capacity Optimization. You can restore access to the database once the upgrade process is complete.
• (On Linux) Edit the <installation directory>\pw\custom\conf\pronet.conf file. Search and remove any duplicate pronet.ps.psName property entries. 
• If you are using a distributed service model, ensure that you set the isDSIMEnabled  parameter to true (isDSIMEnabled=true) in the /pw/custom/conf/pronet.conf file of relevant Infrastructure Management servers and restart them.
• In a cloud-enabled environment, ensure that ensure that you set the isCloudDeployment parameter to true (isCloudDeployment=true) in the /pw/custom/conf/pronet.conf file.
• Ensure that the existing PATROL Agents are registered with their host name FQDNs.
• Ensure that local host is available. For example, if you are using the IPv6 protocol on Linux, run the ping6 command to make sure that the local host is available.

• Take a backup of the httpd-ssl.conf file present in the <Infrastructure Management server Installation directory>\pw\apache\conf\extra directory.

  Note

  If you are importing custom certificates for TrueSight Infrastructure Management server, ensure that you edit the custom certificate and key entries in the httpd-ssl.conf file after you upgrade the TrueSight Infrastructure Management server. For detailed instructions, see  Implementing private certificates in the TrueSight Infrastructure Management.

• Ensure that the ProductRegistry.xml file is present in the following directory with the installed product details:
  
  • (Windows)  C:\Windows
  • (Linux) /opt/bmc/
  If the ProductRegistry.xml is not available, contact BMC Support.

• Based on whether you are upgrading from a small to medium or medium to large, you must update the following parameters in the pronet.conf file:

  File path	Small to Medium	Medium to Large
  (Windows) pw\conf\pronet.conf	pronet.deployment.type=medium pronet.instance.medium.max=60000	pronet.deployment.type=large pronet.instance.large.max=250000
  (Linux) pw/conf/pronet.conf	pronet.deployment.type=medium pronet.instance.medium.max=60000	pronet.deployment.type=large pronet.instance.large.max=250000

• Before you start upgrading, ensure that the environment variables BPPM_SERVER_HOME and BMC_PROACTIVENET_HOME are set and available in the CLI terminal from where the upgrade installer would be triggered.

• Before you start upgrading, ensure that you migrate all the customized KBs, and the migrated KBs are functioning correctly. Also, ensure that the directory path of the migrated KB should follow the hierarchy structure /topLevelDirectory/mergedKB/server/etc/cellName, where /server/etc/cellName is the standard sub-directory. For information about mmigrate utility, see  Using the mmigrate utility.
• If you have custom cells created in your environment, ensure that you stop them before the upgrade and restart them after the upgrade.

• If you have customized service management data in the di_models.baroc file present in the <Infrastructure Management Server Install Directory>\pw\server\etc\<psname> directory, do the following before upgrading the Infrastructure Management Server to ensure that the customized service management data is retained after the upgrade: 

  Do the following before upgrading the Infrastructure Management Server to ensure that the customized service management data is retained:

  Standalone deployment of Infrastructure Management Server

  Do the following:

  1. Take a backup of the <Infrastructure Management Server Install Directory>\pw\server\etc\<psname> directory in a location that is outside the Infrastructure Management Server installation directory.

  2. Ensure that you run the mmigrate utility to merge the cell KB before upgrading the Infrastructure Management Server. This action ensures that the mc_sm_object.baroc file and its customizations are retained after the upgrade.
     Note: Skip this step, if you have already run the mmigrate utility to merge the cell KB.
  3. Upgrade the Infrastructure Management Server.

  4. Copy the publishing server kb from the backup directory to the <Infrastructure Management Server Install Directory>\pw\server\etc\<psname> folder

  High-availability deployment of Infrastructure Management Server

  Perform the steps that are listed for the standalone Infrastructure Management Server first on primary followed by secondary Infrastructure Management Server.

• Stop the Integration Services, event adapters, remote cells that are directly connected to the TrueSight Infrastructure Management server.

• If you have configured a remote cell for the agent controller process, ensure that the following configuration property is updated in the <TrueSight Infrastructure Management installation directory>\pw\custom\conf\pronet.conf file before upgrading the Infrastructure Management server: 

  pronet.pronet_cntl.cellservice.Remotecell.connection.enabled=true

• If you plan to add an additional instance of the Integration Service 11.3.04 on existing Integration Service hosts, ensure that enough resources are available on the host computer.

• To store a backup of the current version of the TrueSight Infrastructure Management server and to copy the installation files for the new version of the TrueSight Infrastructure Management server, ensure that the host machine has a disk space equivalent to the following before upgrading the TrueSight Infrastructure Management server:
  Size of the TrueSight Infrastructure Management server installation directory at <Infrastructure Management server Installation directory> with an additional 3 GB capacity.

• Close all open BMC application windows.

Prerequisites specific to Windows

• If you are planning to upgrade to TrueSight Infrastructure Managementusing the Oracle database running on operating systems with French or German locales enabled, manually grant Administrator access to the dbuser file located in the pw\pronto\conf directory.

• If you are planning to upgrade the TrueSight Infrastructure Management server on an IPv6 Windows host computer, ensure that the IP helper service is started.

• Stop the Service Desk Integration Gateway (SDIG) service (BMC Service Resolution).

Prerequisites specific to Linux

• Ensure that you have at least 4 GB of space in the /tmp directory. This helps the X Windows utility to quickly launch the upgrade GUI utility.

• Ensure that users are not using UNIX/Linux consoles to access the TrueSight Infrastructure Management server(s).

• Ensure that you use the same non-root user that you used while installing the Infrastructure Management server, and has the following permissions:

  • Read, write, and execute permissions for: TrueSight Infrastructure Management installation directory, /var/tmp, /tmp, /usr, and usr/bin directories.
  • Verify the filesystem that the /tmp directory resides in is mounted with exec option by running the findmnt command. If it shows noexec for /tmp, remount it with exec option. For example, mount -o remount,exec /tmp.
  • Execute permission for the /Linux/Disk1/setup.bin file.

  • Read and write permissions for the /opt/bmc directory. 

    Note

    The ProductRegistry.xml file is created in the /opt/bmc directory. Therefore, the /opt/bmc directory requires read and write permissions. If the bmc directory does not exist, create it with read and write permissions.

• You can set these permissions by running the config_nonroot.sh script as a root user. For more information, about running the script, see  Complete the additional tasks for Linux.

• Before upgrading, ensure to note the existing permissions as during a TrueSight Infrastructure Management upgrade which has the CMDB integrations in place, the permissions of the pserver file at /usr/pw/server/bin/pserver might change to 777 (Read, Write, and Execute). You might consider restoring permissions of the pserver file after upgrading to TrueSight Infrastructure Management 11.3.04.
• Ensure that the nslookup binary is installed and available to the user on the machine where you plan to upgrade TrueSight Infrastructure Management.

Database prerequisites 

BMC recommends that you archive the TrueSight Infrastructure Management server database before upgrading the TrueSight Infrastructure Management server.

SAP SQL Anywhere database

Before upgrading, ensure that you take a back up of the SAP SQL Anywhere database. Run the following command to archive the database: 

Oracle database

Before upgrading, ensure that you take a back up of the Oracle database schema related to TrueSight Infrastructure Management. If the upgrade fails, it allows you to restore the database without any loss of data.

Perform the following steps to take the Oracle RAC backup:

1. Stop TrueSight Infrastructure Management by running the pw system stop command.
2. Export the schema created for TrueSight Infrastructure Management by running the EXPDP command. For example, PROACT schema. Take the help of the database administrator to perform this step.

Microsoft .NET Framework prerequisites

On the existing TrueSight Infrastructure Management server that has Microsoft Windows as the operating system, ensure that Microsoft .NET Framework version 3.0 is installed as it is required to use the SCOM adapter. During the upgrade, an error message is displayed if Microsoft .NET Framework is not installed. 

To install .NET Framework on Windows 2008, use the Role Management tool. For more information about how to install the .NET Framework, see  Microsoft web site.

Complete the pre-upgrade tasks for OS high-availability mode (OS cluster)

• Ensure that the cluster configuration is of node and cluster disk majority type.
• Ensure that a visible quorum disk is available.
• Ensure that the HA installer files are not copied to the shared disk.
• Ensure that Microsoft Clustering is installed on the target computer.
• Ensure that before you upgrade, you have migrated the customized KBs in your TrueSight Infrastructure Management implementation. Follow the procedure for executing the KB Migration Wizard described in  Cell configuration migration . When satisfied that the merged KB is working properly, you can begin the server upgrade procedure. Note the directory path of each migrated KB. The directory path must follow this hierarchy structure: /topLevelDirectory/mergedKB/serve/etc/cellName, where /server/etc/cellName is the standard subdirectory.
• For Windows 2012, ensure that the PowerShell execution policy is running in the unrestricted mode.

Where to go from here

If you are upgrading the product, perform the other pre-upgrade tasks listed in the Preparing to upgrade TrueSight Operations Management solution page.