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:
- Download, install, and run the latest version of the TrueSight Health Check Tool.
- 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){{code language="none"}}
$BPPM_SERVER_HOME$/utility/TrueSightHealthCheck/reports
{{/code}} location. {{code language="none" source="string:{{code language=~"none~"~}~}
(% style=~"color: rgb(51,51,51);~" %)
{{/code~}~}"/}}{{/code}}
1. Resolve all the issues.
1. 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.>>doc:confluencePage:page:tsomd11304.Supported upgrade paths for TrueSight Operations Management||target="_blank"]]
)))
* (((
Contact BMC upgrade experts through the[[
AMIGO program>>url:https://communities.bmc.com/docs/DOC-39381||target="_blank"]], 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>>doc:confluencePage:page:tsomd11304.Troubleshooting version 11.3.04 upgrade and post-upgrade issues||target="_blank"]]to ensure that you are aware of workarounds before starting the upgrade.
)))
* Ensure that you have installed the (% style="letter-spacing: 0.0px;" %)**{{code language="none"}}nslookup{{/code}} **(%%)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.>>doc:confluencePage:page:TSOMD11304.Best practices and configuration guidelines for performance and scalability\#On-access virus scanners||target="_blank"]]
)))
* (((
Ensure that you have upgraded the {{display reference="IT-Operations-Management.Operations-Management.TrueSight-Operations-Management.tsomd11307._inclusionsLibrary._variables-1._tspsComponent.WebHome"/}}(% style="color: rgb(0,0,0);letter-spacing: 0.0px;" %) to version 11.3.04. For details about version compatibility matrix, see[[
Presentation Server, Infrastructure Management, and PATROL Agent compatibility matrices.>>doc:confluencePage:page:tsomd11304.Presentation Server, Infrastructure Management, and PATROL Agent compatibility matrices||target="_blank"]](%%)
)))
* (((
Review the[[
System requirements and product compatibility for Infrastructure Management>>doc:confluencePage:page:tsomd11304.System requirements and product compatibility for Infrastructure Management||target="_blank"]] for {{display reference="IT-Operations-Management.Operations-Management.TrueSight-Operations-Management.tsomd11307._inclusionsLibrary._variables-1._tsimComponent.WebHome"/}}.
)))
* 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 {{display reference="IT-Operations-Management.Operations-Management.TrueSight-Operations-Management.tsomd11307._inclusionsLibrary._variables-1._tsimComponent.WebHome"/}} server(s) and Integration Service hosts. For information, see:
** (((
[[Archiving or backing up the Infrastructure Management Server>>doc:confluencePage:page:tsim11304.Archiving or backing up the Infrastructure Management Server||target="_blank"]]
)))
** (((
[[
Backing up configuration and database files (SAP SQL Anywhere)>>doc:confluencePage:page:tsim11304.Backing up configuration and database files (SAP SQL Anywhere)||target="_blank"]]
{{confluence_note icon="false" title="Additional 7 GB disk space"}}
(% style="color: rgb(51, 51, 51); color: rgb(51, 51, 51)" %)Ensure that the host machine has (% style="color: rgb(51, 51, 51); color: rgb(51, 51, 51); color: rgb(51, 51, 51)" %)an additional 7 GB (% style="color: rgb(51, 51, 51); color: rgb(51, 51, 51)" %)disk space t(% style="color: rgb(51,51,51);" %)o store a backup of the existing (% class="conf-macro" %)TrueSight Infrastructure Management(% style="color: rgb(51,51,51);" %) server, which is (%%)automatically created during the upgrade process(% style="color: rgb(51,51,51);" %) and to copy the installation files for the new version of the (% class="conf-macro" %)TrueSight Infrastructure Management(% style="color: rgb(51,51,51);" %) 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.
{{/confluence_note}}
)))
* 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.
* (% style="color: rgb(0,0,0);" %)Stop access to the {{display reference="IT-Operations-Management.Operations-Management.TrueSight-Operations-Management.tsomd11307._inclusionsLibrary._variables-1._tsimComponent.WebHome"/}} database from other BMC products such as {{display reference="IT-Operations-Management.Operations-Management.TrueSight-Operations-Management.tsomd11307._inclusionsLibrary._variables-1._solutionName.WebHome"/}} Reporting, or {{display reference="IT-Operations-Management.Operations-Management.TrueSight-Operations-Management.tsomd11307._inclusionsLibrary._variables-1._tsoProduct.WebHome"/}}. 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 (% style="letter-spacing: 0px; color: rgb(0, 51, 102)" %)**pronet.ps.psName**(%%) property entries.
* If you are using a distributed service model, ensure that you set the (% style="letter-spacing: 0.0px;" %){{code language="none"}}isDSIMEnabled{{/code}}(%%) parameter to true ((% style="letter-spacing: 0.0px;" %){{code language="none"}}isDSIMEnabled=true{{/code}}(%%)) in the (% style="letter-spacing: 0.0px;" %)**/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 {{code language="none"}}isCloudDeployment{{/code}} parameter to true ({{code language="none"}}isCloudDeployment=true{{/code}}) 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 {{code language="none"}}ping6{{/code}} 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.
{{confluence_note title="Note"}}
If you are importing custom certificates for {{display reference="IT-Operations-Management.Operations-Management.TrueSight-Operations-Management.tsomd11307._inclusionsLibrary._variables-1._tsimComponent.WebHome"/}} server, ensure that you edit the custom certificate and key entries in the **httpd-ssl.conf** file after you upgrade the {{display reference="IT-Operations-Management.Operations-Management.TrueSight-Operations-Management.tsomd11307._inclusionsLibrary._variables-1._tsimComponent.WebHome"/}} server. For detailed instructions, see [[
Implementing private certificates in the TrueSight Infrastructure Management.>>doc:confluencePage:page:tsomd11304.Implementing private certificates in the TrueSight Infrastructure Management\#TosecuretheInfrastructureManagementservertobrowsercommunication||target="_blank"]]
{{/confluence_note}}
)))
* (((
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 **{{code language="none"}}pronet.conf{{/code}} **file:
|=(((
File path
)))|=(((
Small to Medium
)))|=(((
Medium to Large
)))
|(((
(//Windows//)
**{{code language="none"}}pw\conf\pronet.conf{{/code}}**
)))|(((
* pronet.deployment.type=medium
* pronet.instance.medium.max=60000
)))|(((
* pronet.deployment.type=large
* pronet.instance.large.max=250000
)))
|(((
(//Linux//)
**{{code language="none"}}pw/conf/pronet.conf{{/code}}**
)))|(((
* 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.>>doc:IT-Operations-Management.Operations-Management.BMC-TrueSight-Operations-Management.TSOMD11304.Upgrading.Using-the-mmigrate-utility.WebHome||target="_blank"]]
)))
* If you have custom cells created in your environment, ensure that you stop them before the upgrade and restart them after the upgrade.
* (((
(% style="color: rgb(0,0,0);" %)If you have customized service management data in the (%%)**di_models.baroc**(% style="color: rgb(0,0,0);" %) file present in the (%%)**<Infrastructure Management Server Install Directory>\pw\server\etc\<psname>**(% style="color: rgb(0,0,0);" %) directory, do the following before upgrading the Infrastructure Management Server to ensure that the customized service management data is retained after the upgrade:
{{error title="Do the following before upgrading the Infrastructure Management Server to ensure that the customized service management data is retained:"}}
==== {{id name="PreparingtoupgradeInfrastructureManagement-StandalonedeploymentofInfrastructureManagementServer"/}}{{id name="PreparingtoupgradeInfrastructureManagement-standalone_cmdb"/}}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.
1. Ensure that you run the {{code language="none"}}mmigrate{{/code}} 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 {{code language="none"}}mmigrate{{/code}} utility to merge the cell KB.
1. Upgrade the Infrastructure Management Server.
1. Copy the publishing server kb from the backup directory to the **<Infrastructure Management Server Install Directory>\pw\server\etc\<psname>** folder
==== {{id name="PreparingtoupgradeInfrastructureManagement-High-availabilitydeploymentofInfrastructureManagementServer"/}}High-availability deployment of Infrastructure Management Server ====
(% style="margin-left: 2.0pt;" %)
Perform the steps that are listed for the standalone Infrastructure Management Server first on primary followed by secondary Infrastructure Management Server.
{{/error}}
)))
* Stop the Integration Services, event adapters, remote cells that are directly connected to the {{display reference="IT-Operations-Management.Operations-Management.TrueSight-Operations-Management.tsomd11307._inclusionsLibrary._variables-1._tsimComponent.WebHome"/}} 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:
{{code}}
pronet.pronet_cntl.cellservice.Remotecell.connection.enabled=true
{{/code}}
)))
* 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 {{display reference="IT-Operations-Management.Operations-Management.TrueSight-Operations-Management.tsomd11307._inclusionsLibrary._variables-1._tsimComponent.WebHome"/}} server and to copy the installation files for the new version of the {{display reference="IT-Operations-Management.Operations-Management.TrueSight-Operations-Management.tsomd11307._inclusionsLibrary._variables-1._tsimComponent.WebHome"/}} server, ensure that the host machine has a disk space equivalent to the following before upgrading the {{display reference="IT-Operations-Management.Operations-Management.TrueSight-Operations-Management.tsomd11307._inclusionsLibrary._variables-1._tsimComponent.WebHome"/}} server:
Size of the {{display reference="IT-Operations-Management.Operations-Management.TrueSight-Operations-Management.tsomd11307._inclusionsLibrary._variables-1._tsimComponent.WebHome"/}} server installation directory at **<Infrastructure Management server Installation directory>** with an additional 3 GB capacity.
* Close all open BMC application windows.
=== {{id name="PreparingtoupgradeInfrastructureManagement-PrerequisitesspecifictoWindows"/}}Prerequisites specific to Windows ===
* If you are planning to upgrade to {{display reference="IT-Operations-Management.Operations-Management.TrueSight-Operations-Management.tsomd11307._inclusionsLibrary._variables-1._tsimComponent.WebHome"/}}(% style="color: rgb(0,0,0);" %)using 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**(% style="color: rgb(0,0,0);" %) directory.
* (% style="color: rgb(0,0,0);" %)If you are planning to upgrade the {{display reference="IT-Operations-Management.Operations-Management.TrueSight-Operations-Management.tsomd11307._inclusionsLibrary._variables-1._tsimComponent.WebHome"/}} server on an IPv6 Windows host computer, ensure that the //IP helper// service is started.
* (% style="color: rgb(0,0,0);" %)Stop the Service Desk Integration Gateway (SDIG) service (BMC Service Resolution).
=== {{id name="PreparingtoupgradeInfrastructureManagement-PrerequisitesspecifictoLinux"/}}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 {{display reference="IT-Operations-Management.Operations-Management.TrueSight-Operations-Management.tsomd11307._inclusionsLibrary._variables-1._tsimComponent.WebHome"/}} 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: (% class="conf-macro output-block" %)**TrueSight Infrastructure Management**(%%)** installation directory**,** /var/tmp**, **/tmp**,** /usr, **and **usr/bin** directories.
** Verify the filesystem that the (% style="letter-spacing: 0.0px;" %)**/tmp**(%%) directory resides in is mounted with (% style="letter-spacing: 0.0px;" %)**exec**(%%) option by running the (% style="letter-spacing: 0.0px;" %)**findmnt**(%%) command. If it shows (% style="letter-spacing: 0.0px;" %)**noexec**(%%) for (% style="letter-spacing: 0.0px;" %)**/tmp**(%%), remount it with (% style="letter-spacing: 0.0px;" %)**exec**(%%) option. For example, (% style="letter-spacing: 0.0px;" %)**mount -o remount,exec /tmp**(%%).
** Execute permission for the **/Linux/Disk1/setup.bin **file.
** (((
Read and write permissions for the (% style="letter-spacing: 0.0px;" %)**/opt/bmc**(%%) directory.
{{confluence_note title="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.
{{/confluence_note}}
)))
* (((
You can set these permissions by running the **{{code language="none"}}config_nonroot.sh{{/code}}** script as a root user. For more information, about running the script, see [[
Complete the additional tasks for Linux.>>doc:confluencePage:page:TSOMD11304.Preparing to install Infrastructure Management\#Complete the additional tasks for Linux||target="_blank"]]
)))
* Before upgrading, ensure to note the existing permissions as during a {{display reference="IT-Operations-Management.Operations-Management.TrueSight-Operations-Management.tsomd11307._inclusionsLibrary._variables-1._tsimComponent.WebHome"/}} 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 {{display reference="IT-Operations-Management.Operations-Management.TrueSight-Operations-Management.tsomd11307._inclusionsLibrary._variables-1._tsimComponent.WebHome"/}} 11.3.04.
* Ensure that the nslookup binary is installed and available to the user on the machine where you plan to upgrade {{display reference="IT-Operations-Management.Operations-Management.TrueSight-Operations-Management.tsomd11307._inclusionsLibrary._variables-1._tsimComponent.WebHome"/}}.
Database prerequisites
BMC recommends that you archive the TrueSight Infrastructure Management server database before upgrading the TrueSight Infrastructure Management server.
TrueSight Infrastructure Management is supported on the 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:
- Stop TrueSight Infrastructure Management by running the pw system stop command.
- 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.
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*