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:
Prerequisites common to Windows and Linux
- 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 .
- Contact BMC upgrade experts through the , and upgrade only after they confirm that the environment is ready for an upgrade.
- 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
- Ensure that you have upgraded the TrueSight Presentation Server to version 11.3.01. For details about version compatibility matrix, see
- Review the 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, copy snapshots of the TrueSight Infrastructure Management server(s) and Integration Service hosts. For information, see:
- 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.
- If you are using a distributed service model, ensure that you set the
isDSIMEnabledparameter 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
isCloudDeploymentparameter 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
ping6command 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.
- Ensure that the ProductRegistry.xml file is present in the following directory with the installed product details:
- (Windows) C:\Windows
- (Linux) /opt/bmc/
Based on whether you are upgrading from a small to medium or medium to large, you must update the following parameters in the
File path Small to Medium Medium to Large
- 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 infromation about mmigrate utility, see
- 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:
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.
- Ensure that you run the
mmigrateutility 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
mmigrateutility to merge the cell KB.
- Upgrade the Infrastructure Management Server.
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 plan to add an additional instance of the Integration Service 11.3.01 on existing Integration Service hosts, ensure that enough resources are available on the host computer.
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.
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.
- Execute permission for the /Linux/Disk1/setup.bin file.
Read and write permissions for the /opt/bmc directory.
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.shscript as a root user. For more information, about running the script, see
BMC recommends that you archive the TrueSight Infrastructure Management server database before upgrading the TrueSight Infrastructure Management server.
You cannot automatically upgrade the TrueSight Infrastructure Management server with a SAP SQL Anywhere database to a TrueSight Infrastructure Management server with Oracle database or TrueSight Infrastructure Management server with a Oracle database to a TrueSight Infrastructure Management server with SAP SQL Anywhere database.
Contact BMC Services Account Manager or BMC Support for assistance.
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:
If the upgrade fails, run the
pw database restore command to restore the database from the archive directory. For more information about the
pw database restore command, see
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:
- Stop TrueSight Infrastructure Management by running the
pw system stopcommand.
- Export the schema created for TrueSight Infrastructure Management by running the
EXPDPcommand. For example, PROACT schema. Take the help of the database administrator to perform this step.
If the upgrade fails, perform the following to restore the database:
- Perform one of the following steps:
- If you are using a Oracle Recovery Manager (RMAN), take the database administrator's help to perform a point-in-time recovery.
- If you have used the
EXPDPcommand to take a backup of the schema, take the database administrator's help to import the schema by using the
- Restore TrueSight Infrastructure Management to the previous functioning version.
Note: If you have accessed TrueSight Infrastructure Management by using the Report user, you have read-only access to the Oracle database. The Report user does not have any objects that are available for a backup.
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
The installation of .NET Framework might take several minutes to complete.
Complete the pre-upgrade tasks for application high-availability mode
- 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 the HA installer files are not copied to the shared disk.
- 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 . 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.
When you upgrade TrueSight Infrastructure Management on a 64-bit operating system, the JServer, Rate, and Agent Controller processes use 64-bit JRE, and the Self-monitoring Service process uses 64-bit JRE on Windows and 32-bit JRE on Solaris. If you have already configured the 64-bit JRE processes in an earlier version of TrueSight Infrastructure Management, they are retained.
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.